-
New Feature
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins ver. 2.63
So, I'm having this problem that I described in a similar bug for the lockable-resource plugin (JENKINS-45138). I said to myself, "oh, hey, I remember being able to throttle executions on a per-agent basis!"
Imagine my surprise when I hit the documentation and find that throttle is only applicable inside a step.
I need to acquire, use, and cleanup exclusive access to a resource on each agent. Will throttle work how I expect?
step('foo') { throttle(['foo-label']) bat '... acquire the resource...' bat '... use the resource...' } post { always { bat '... cleanup the resource...' } }
[JENKINS-45140] Add support of throttling of the entire build in Declarative Pipeline
Summary | Original: How do I throttle an entire declarative pipeline job? | New: How do I throttle an entire declarative pipeline job per-agent? |
Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
Summary | Original: How do I throttle an entire declarative pipeline job per-agent? | New: Add support of throttling of the entire build in Declarative Pipeline |
Component/s | New: pipeline-model-definition-plugin [ 21706 ] |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Attachment | New: set-job-properties.png [ 38815 ] |
Attachment | New: throttle-entire-job.png [ 39008 ] |
Assignee | New: Andrew Bayer [ abayer ] | |
Resolution | Original: Not A Defect [ 7 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Attachment | New: image-2018-09-21-18-20-12-512.png [ 44558 ] |