This is the idiom to get what you are looking for:
https://github.com/jenkinsci/workflow-aggregator-plugin/blob/master/demo/repo/Jenkinsfile#L22-L36
On Wed, Sep 28, 2016 at 12:49 AM, James Nord wrote:
> The new way to do this is with a milestone.
>
> https://wiki.jenkins-ci.org/display/JENKINS/P
The new way to do this is with a milestone.
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Milestone+Step+Plugin
--
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 em
Thanks - last I checked it was not finished - now it is! :)
2016-09-21 23:37 GMT+02:00 Michael Kobit :
> I believe the stage step with concurrency has been deprecated so I would
> avoid using that.
>
> It sounds like you are looking for https://issues.jenkins-ci.org/
> plugins/servlet/mobile#issu
I believe the stage step with concurrency has been deprecated so I would avoid
using that.
It sounds like you are looking for
https://issues.jenkins-ci.org/plugins/servlet/mobile#issue/JENKINS-27039
(milestone step).
--
You received this message because you are subscribed to the Google Groups
I have a question on locks vs stage w/ concurrency:
lock(inversePrecedence: true, resource: 'myLock') {
// some block
}
vs
stage(name:'myStage',concurrency:1) {
// some block
}
With stages newer builds would "win" over older ones while waiting to run
s
