On Thursday, December 11, 2014 1:29:06 PM UTC-8, Jesse Glick wrote: > (Whether this step is important for a broad enough class of users to > merit direct mention is another question. Newly written flows can
Right -- I guess I was just surprised not to see it mentioned, since it seemed like a pretty important feature. But maybe that's because I was thinking in terms of migration. I don't understand what is exposed to flows enough to know if newly written flows would never need to use 'old-style' jenkins jobs. For instance, our build job uses the ec2 plugin to dynamically manage ec2 machines running the build slaves; I wouldn't know how to get the same functionality via groovy, if we were trying to re-implement things from scratch. > I do not think flows should be writing such code directly. Probably > this should just be an option for the parallel step (or even the > standard behavior). Feel free to file it as an RFE. Just to be clear: by "this" do you mean: canceling sibling jobs when a job inside 'parallel' fails? I'm glad to file an RFE. Where is the right place to file it? Another thing I was unclear on: does 'parallel' have a return value? (Do steps have a return value in general?) If I had 'parallel [ nodeA: ..., nodeB: ...]' and nodeA failed, would I have some way of telling that things failed? > Do you have other use cases for such a feature, besides just making > parallel fail early? I can think of others -- for instance, implementing a more sophisticated timeout functionality. Say I wanted to run jobA and jobB in parallel, but if one job took more than 10 minutes longer than the other job, I'd cancel the whole thing. This is pretty contrived though. My instinct is that having access to a 'job' object that lets you query what's going on with a running job would be a useful thing to have. But for now -- and I say this not having tried to re-implement our deploy process yet -- the parallel-fail case is the only one I think we really need. Thanks for the quick reply! 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/f9ba0928-3f6f-46c8-a056-de9a977619a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
