In Pipeline we splice in the folder name to create lock resources for this
reason. Note these are artificial, abstract resources created on the fly by
the pipelines themselves just to have concurrency guards across pipelines
in a folder. They don't correspond to any real concrete resource.
//Chop the base job name, e.g. foo/bar/do-this > foo/bar.
final folder = JOB_NAME.replaceFirst( '/[^/]+$', '' )
lock( resource: "$folder::$stageName", inversePrecedence: true ) {
stage(stageName) {
...
I can't speak to lock permissions; we're not to that level of complexity
yet.
On Sunday, June 3, 2018 at 2:15:04 PM UTC-7, John Lonergan wrote:
>
> Any info on scoped locks?
> Server wide locks are a problem on a big instance as we get colliding
> names.
--
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/bb1a2038-09ac-4308-940d-55459a5a3626%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
