-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
CentOS Linux release 7.3.1611 (Core)
java version "1.8.0_101"
Several times now, I have seen the instance where a single job is taking up all of the locks with the specified label while the quantity is set to 1. The pipeline code is as follows:
{{
// Pipeline Details
def pipelineName = "pr-pipeline"
def lockLabel = "pr-pipeline"
def lockQuantity = 1
// Pipeline
lock(label: lockLabel, quantity: lockQuantity)
The attached picture is a single job taking up all of the resources with the label. I'm not sure how this situation arises,
- duplicates
-
JENKINS-40879 Locked areas are executed multiple times in parallel
-
- Closed
-
[JENKINS-41858] Label + Quantity is sometimes not honored
Description |
Original:
Several times now, I have seen the instance where a single job is taking up all of the locks with the specified label while the quantity is set to 1. The pipeline code is as follows: {{// Pipeline Details def pipelineName = "pr-pipeline" def lockLabel = "pr-pipeline" def lockQuantity = 1 // Pipeline lock(label: lockLabel, quantity: lockQuantity) { ... the code ... }} The attached picture is a single job taking up all of the resources with the label. I'm not sure how this situation arises, |
New:
Several times now, I have seen the instance where a single job is taking up all of the locks with the specified label while the quantity is set to 1. The pipeline code is as follows: {{ // Pipeline Details def pipelineName = "pr-pipeline" def lockLabel = "pr-pipeline" def lockQuantity = 1 // Pipeline lock(label: lockLabel, quantity: lockQuantity) { ... the code ... }} The attached picture is a single job taking up all of the resources with the label. I'm not sure how this situation arises, |
Link |
New:
This issue relates to |
Link |
Original:
This issue relates to |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Seems like this could be the same issue