Re: Is `concurrency: 1` on a stage in multibranch pipeline build supposed to apply to all branches for that build?

Was watching the new release notes for some plugins, and happened to find this: JENKINS-34547 Converted concurrency setting to a job property, allowing it to be defined in a multibranch Jenkinsfile via the properties step. It looks like it

Re: Is `concurrency: 1` on a stage in multibranch pipeline build supposed to apply to all branches for that build?

I never found a good solution, but I am using the lockable resources plugin (https://wiki.jenkins-ci.org/display/JENKINS/Lockable+Resources+Plugin). I didn't need to define each resource manually: When the lock step is used in a Pipeline, if the resource to be locked > isn't already defined in

Re: Is `concurrency: 1` on a stage in multibranch pipeline build supposed to apply to all branches for that build?

Hi David, Did you ever find a nice solution to this problem? I would also like to lock builds for projects with multiple branches / PRs, but don't want to mess with using lockable resources (which seems to be the only solution right now that works with pipeline code, but it requires you define

Is `concurrency: 1` on a stage in multibranch pipeline build supposed to apply to all branches for that build?

I have a Jenkinsfile in my repo, and one of the stages uses resources shared across every branch, but I need to limit it to only one build at a time. It seems that if two branches are being built simultaneously, they don't respect the concurrency parameter and end up using the shared resource a