-
New Feature
-
Resolution: Duplicate
-
Minor
-
None
If we `unreserve` some resource from webui, the resource does not appear as available to jobs already waiting for resource with label that matches this resources label.
I would expect that `unreserve` should have the same behavior as unlock step, thus unreserving a resource should allow jobs waiting on this resource to acquire normally.
- duplicates
-
JENKINS-34433 Pipeline locks not signalled on manual unreserving of resources
-
- Resolved
-
[JENKINS-46745] Unreserve resource should make resource available to running jobs like unlock step does.
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Experiencing this, with the 2.0 version.
I think this is rather a bug fix than a new feature.
The thread of the running build appears to be stuck on the lock:
Thread #90 at DSL.lock(Native Method) at WorkflowScript.run(WorkflowScript:28) at DSL.stage(Native Method) ...