Yes, there's a more sophisticated way of doing this now. Here's a good blog post <https://jenkins.io/blog/2016/10/16/stage-lock-milestone> on the technique.
On Monday, October 17, 2016 at 10:44:49 AM UTC-7, Kyle Flavin wrote: > > I posted this in the wrong place previously - hope this is correct. > > Does the concurrency parameter no longer apply to the stage block? This > post is in reference to: > https://issues.jenkins-ci.org/browse/JENKINS-26107 > > I have some legacy code, and I'm converting "stage" to use the new block > format. We have a lot of stuff that looks like this: > > > stage name: 's1: do something', concurrency: 1 > ... > > stage name: 's2: do something else', concurrency: 1 > ... > > > > I'm not entirely sure what "concurrency" is doing, or if it's even > necessary to preserve in this case. I can't find much reference to the new > form in the docs. Is it safe to just ignore the parameter? Is it handled > in some other way now?: > > > stage("s1: do something") { > ... > > } > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5b949ba8-f6ac-45ba-bc44-1643331eb3fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
