OK, RFE's filed at https://issues.jenkins-ci.org/browse/JENKINS-26033 https://issues.jenkins-ci.org/browse/JENKINS-26034
The following is just FYI: On Thursday, December 11, 2014 3:14:00 PM UTC-8, Jesse Glick wrote: > If you mean you just want to run on an EC2 slave, that is covered by ‘node’. 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). I presume the 'workflow' way of handling this is to have the plugin expose the necessary functionality via a SimpleBuildStep, and then I could call it. I'm not exactly sure what functionality that would be in this case; I don't really understand where the ec2 plugin hooks in to jenkins, though it seems rather complicated. > > If I had 'parallel [ nodeA: ..., nodeB: ...]' and nodeA failed, would I have some way of telling that things failed? > The whole ‘parallel’ step would fail in this case. So 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, if anything. If we saw something failed, we'd log it and then manually fail the deploy job, otherwise we'd just go on to the next deploy step. Thanks for this project, btw! I've been checking in from time to time and have seen how actively it's being developed. I am very excited to play around with it. craig -- 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/cf3c9f58-bfff-4f0c-b6f7-97df4c86f401%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
