-
Bug
-
Resolution: Fixed
-
Minor
-
None
The docs suggest that marking a stage with "concurrency: 1" will allow only the latest build to run, and that if older builds reach such a section, it will stop executing:
"The stage command lets you mark certain sections of a build as being constrained by limited concurrency.
Newer builds are always given priority when entering such a throttled stage; older builds will simply exit early if they are preëmpted."
I instead observed an older build simply waiting until a newer build had finished, and then continuing to run the concurrency: 1 section.
This is a problem for us this is our deploy stage, and we wish to only deploy the latest code.
- is related to
-
JENKINS-27039 Option for input or stage step to cancel older executions
-
- In Review
-
- links to
[JENKINS-32829] Older builds allowed to wait for a throttled stage which a newer build is in
Marcus Cobden
created issue -
| Link |
New:
This issue is related to |
| Summary | Original: Pre-empted builds not stopped in stage with concurrency:1 | New: Older builds allowed to wait for a throttled stage which a newer build is in |
| Remote Link | New: This issue links to "PR 355 (Web Link)" [ 14037 ] |
| Workflow | Original: JNJira [ 168521 ] | New: JNJira + In-Review [ 183158 ] |
| Component/s | New: pipeline-general [ 21692 ] |
| Component/s | Original: workflow-plugin [ 18820 ] |
| Component/s | New: pipeline-milestone-step-plugin [ 21448 ] | |
| Component/s | New: pipeline-stage-step-plugin [ 21709 ] | |
| Component/s | Original: pipeline [ 21692 ] |
| Assignee | Original: Jesse Glick [ jglick ] | New: Antonio Muñiz [ amuniz ] |
| Remote Link | Original: This issue links to "PR 355 (Web Link)" [ 14037 ] |
| Remote Link | New: This issue links to "milestone step PR (Web Link)" [ 14862 ] |