-
Bug
-
Resolution: Fixed
-
Critical
-
Jenkins 2.7.1
Jenkins 2.49
Pipeline plugin 2.4
-
-
Jenkins 2.136
I have configured a Jenkins pipeline to disable concurrent builds:
properties([ disableConcurrentBuilds() ])
However, I have noticed on some occasions the next 2 builds are pulled from the pipeline's queue and executed concurrently. Why this occurs is not obvious at all.
- relates to
-
JENKINS-30231 Build creates second workspace@2 for non-concurrent build configuration
-
- Resolved
-
- links to
[JENKINS-41127] Multiple pipeline instances running concurrently when concurrent execution disabled
Description |
Original:
I have configured a Jenkins pipeline to disabled concurrent builds: {code} properties([ disableConcurrentBuilds() ]) {code} However, I have noticed on some occasions multiple instances of the pipeline execute concurrently. This seems to happen when the pipeline is triggered by an upstream job at the same time that a user manually triggers it - possible race condition? |
New:
I have configured a Jenkins pipeline to disable concurrent builds: {code} properties([ disableConcurrentBuilds() ]) {code} However, I have noticed on some occasions multiple instances of the pipeline execute concurrently. This seems to happen when the pipeline is triggered by an upstream job at the same time that a user manually triggers it - possible race condition? |
Description |
Original:
I have configured a Jenkins pipeline to disable concurrent builds: {code} properties([ disableConcurrentBuilds() ]) {code} However, I have noticed on some occasions multiple instances of the pipeline execute concurrently. This seems to happen when the pipeline is triggered by an upstream job at the same time that a user manually triggers it - possible race condition? |
New:
I have configured a Jenkins pipeline to disable concurrent builds: {code} properties([ disableConcurrentBuilds() ]) {code} However, I have noticed on some occasions multiple instances of the pipeline execute concurrently. This seems to happen when the pipeline is triggered by an upstream job at the same time that a user manually triggers it - possible race condition? Will attach logs when this occurs again, don't currently have them available. |
Environment |
Original:
Jenkins 2.7.1 Pipeline plugin 2.4 |
New:
Jenkins 2.7.1 Jenkins 2.49 Pipeline plugin 2.4 |
Component/s | New: workflow-job-plugin [ 21716 ] | |
Component/s | Original: pipeline [ 21692 ] |
Labels | Original: bug concurrent pipeline | New: concurrent |
Bump. Seeing this again. My pipeline is configured to disable concurrent builds, yet I saw two instances running when they were both triggered at exactly the same time, down to the second. Jenkins version now is 2.49.