Re: locks vs stage w/concurrency

2016-10-03 Thread Antonio Muñiz
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/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
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/a5a52abd-4e15-46c3-9d3b-4ca5522fe110%40googlegroups.
> com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Antonio Muñiz
Software Engineer
CloudBees, Inc.

-- 
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/CAJc7kzR9fhh14iA6DZc0TmMZvwHfgYD3m-EpbaRqtOASPVdAJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: locks vs stage w/concurrency

2016-09-21 Thread David Karlsen
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#issue/JENKINS-27039 (milestone step).
>
> --
> 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/c758e13a-c59c-4c8b-a0a6-36645c57477c%40googlegroups.
> com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

-- 
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/CAGO7Ob0V0yTXAZ4JCb2bJ7JAowbBrAM8OUh4A27rr3Rbho%2BwiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


locks vs stage w/concurrency

2016-09-21 Thread 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#issue/JENKINS-27039 
(milestone step).

-- 
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/c758e13a-c59c-4c8b-a0a6-36645c57477c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


locks vs stage w/concurrency

2016-09-21 Thread David Karlsen
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
so that unnecessary was avoided, however with locks all builds will run - I
want the newer job to wait for a lock to win, and the ones that became
stale to disappear - this does not seem possible?


-- 
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

-- 
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/CAGO7Ob0AXiyyZqea7KNLWPJO7dyXO8H6KGmymqrwp__M7Ngdzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.