HI, I'm not clear on your use case but BuildFlowExtensions[1] contains a "block" DSL that may help you.
The block DSL ensures that only one Run (build) of a particular BuildFlow > will execute the steps contained within it concurrently. > It further will only allow the most recent FlowRun to proceed if multiple > become blocked. > It is expected that the blockName will only be used once in a Flow - using > the blockname multiple times will work, however the results may not be what > the user intended). > > If the block is not executed then the flow will be aborted. > /James [1] https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Extensions+Plugin On Thursday, 19 February 2015 00:36:41 UTC, Jim Adams wrote: > > I am using the BuildFlow plugin to attempt to sequence a whole bunch of > builds. The same build could be queued by different build flow jobs. The > problem is that if the different build flow jobs are run at the same time > one will fail if the other has already enqueued the job. Is there a way to > just simply skip that build? Or wait for it to end without enqueuing it? > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/ba7479fe-0048-4a3d-88c9-51d3d182cfe8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
