On Thu, Dec 11, 2014 at 7:58 PM, Craig Silverstein <[email protected]> wrote: > I do mean running on an ec2 slave, but the ec2 plugin dynamically brings up > ec2 instances for the slaves to run on (and then shuts them down again after > a timeout).
That should be an automatic aspect of the EC2 plugin’s Cloud implementation. (I have not personally tried it with this plugin yet.) In other words, unless there is some bug I do not know about yet, you should not need to do anything special at all: just configure an EC2 cloud with some label, then pass that label to ‘node’. > if we wanted to log the fact that it was nodeA that failed, it sounds > like what we'd do is wrap the 'parallel' step in a let-it-fail construct, > and then examine the return value of parallel to see what failed As noted in JENKINS-26033, it is clearer and easier (IMO) to use a try/catch block inside the parallel branch. You can then decide how to proceed in the catch block: rethrow the exception as is, throw up a polite error (JENKINS-25924), record some information in a variable accessible to the closure, etc. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2hSYPaZ1zJQ9cBH54cZpwN_eTUVn%3DPwVK1Q6F%3DO%2BJJ5A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
