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.
