-
New Feature
-
Resolution: Duplicate
-
Minor
-
None
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!
- 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