Details
-
Type:
New Feature
-
Status: Resolved (View Workflow)
-
Priority:
Minor
-
Resolution: Duplicate
-
Component/s: pipeline
-
Labels:None
-
Similar Issues:
Description
My use case is users launching multiple jobs that use a lot of server bandwidth, so I would prefer to do something that limits the number of stages running concurrently similar to:
stage 'start' stage name: 'bandwidth-hog', concurrency: 5, resourceLock: true //bandwidth hogging code stage 'finish'
However, I can't have newer jobs pre-empt older jobs, they should just be queued up. Of course, this could be a new step as well. Hopefully this helps others as well!
Attachments
Issue Links
- duplicates
-
JENKINS-30269 Add workflow support for resource locking
-
- Resolved
-
- is related to
-
JENKINS-27039 Option for input or stage step to cancel older executions
-
- In Review
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue is related to |
Description |
My use case is users launching multiple jobs that use a lot of server bandwidth, so I would prefer to do something that limits the number of stages running concurrently similar to: {code} stage 'start' stage name: 'bandwidth-hog', concurrency: 5, resourceLock: true //bandwidth hogging code stage 'finish' {code} It would be useful if newer jobs did not pre-empt older jobs, but just queued up. Of course, this could be a new step as well. Hopefully this helps others as well! |
My use case is users launching multiple jobs that use a lot of server bandwidth, so I would prefer to do something that limits the number of stages running concurrently similar to: {code} stage 'start' stage name: 'bandwidth-hog', concurrency: 5, resourceLock: true //bandwidth hogging code stage 'finish' {code} However, I can't have newer jobs pre-empt older jobs, they should just be queued up. Of course, this could be a new step as well. Hopefully this helps others as well! |
Link |
This issue duplicates |
Resolution | Duplicate [ 3 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Workflow | JNJira [ 165884 ] | JNJira + In-Review [ 197841 ] |
Component/s | pipeline-general [ 21692 ] |
Component/s | workflow-plugin [ 18820 ] |
stage is not designed for this use case; a separate step would be more appropriate.