Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
Jenkins 2.7.1
Jenkins 2.49
Pipeline plugin 2.4
-
-
Jenkins 2.136
Description
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.
Attachments
Issue Links
- relates to
-
JENKINS-30231 Build creates second workspace@2 for non-concurrent build configuration
-
- Resolved
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Description |
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? |
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 |
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? |
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 |
Jenkins 2.7.1 Pipeline plugin 2.4 |
Jenkins 2.7.1 Jenkins 2.49 Pipeline plugin 2.4 |
Component/s | workflow-job-plugin [ 21716 ] | |
Component/s | pipeline [ 21692 ] |
Labels | bug concurrent pipeline | concurrent |
Component/s | throttle-concurrent-builds-plugin [ 15745 ] | |
Component/s | workflow-job-plugin [ 21716 ] |
Component/s | workflow-job-plugin [ 21716 ] | |
Component/s | throttle-concurrent-builds-plugin [ 15745 ] |
Description |
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. |
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 for no apparent reason; the next 2 builds are pulled from the queue and exited at the same time. |
Description |
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 for no apparent reason; the next 2 builds are pulled from the queue and exited at the same time. |
I have configured a Jenkins pipeline to disable concurrent builds: {code} properties([ disableConcurrentBuilds() ]) {code} 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. |
Priority | Major [ 3 ] | Critical [ 2 ] |
Component/s | core [ 15593 ] | |
Component/s | workflow-job-plugin [ 21716 ] |
Remote Link | This issue links to "CloudBees Internal CD-436 (Web Link)" [ 20566 ] |
Link |
This issue relates to |
Remote Link | This issue links to "CloudBees Internal CD-437 (Web Link)" [ 21211 ] |
Remote Link | This issue links to "jenkinsci/jenkins#3562 (Web Link)" [ 21228 ] |
Assignee | Devin Nusbaum [ dnusbaum ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Released As | Jenkins 2.136 | |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Labels | concurrent | concurrent lts-candidate |
Labels | concurrent lts-candidate | 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.