-
Improvement
-
Resolution: Fixed
-
Minor
-
None
Extend the use of quantity configuration parameter to the lock step.
The behavior should be the same than defined for freestyle builds.
The DSL should look like this:
lock (resource: 'RAM', quantity: 3) { ... }
quantity must be applicable to any of resource, resources or label (see JENKINS-34268).
- is related to
-
JENKINS-34268 Lock multiple resources using the Pipeline lock step
- Resolved
-
JENKINS-30269 Add workflow support for resource locking
- Resolved
-
JENKINS-42339 each lockable resource should have a quantity field which defaults to 1
- Open
- links to