-
New Feature
-
Resolution: Fixed
-
Minor
-
None
When a build is not able to acquire a lock, the only way to know what build is holding the lock is to go to the Lockable Resources manager screen. Also there could be several builds in the queue waiting in front of that build.
The console out put only provides information about the fact that the resources are not available:
Trying to acquire lock on [<resourceName>]
Found 0 available resource(s). Waiting for correct amount: 1.
[<resourceName>] is locked, waiting...
It would be great if the console output could provide information about what build(s) we are waiting for and/or how many builds we are waiting for.
- links to
[JENKINS-50618] Provide information in the console about who owns a lock when waiting
Allan BURDAJEWICZ
created issue -
| Remote Link | New: This issue links to "CloudBees Internal CD-458 (Web Link)" [ 20539 ] |
Tobias Gruetzmacher
made changes -
| Released As | New: https://github.com/jenkinsci/lockable-resources-plugin/releases/tag/lockable-resources-2.6 | |
| Assignee | New: Tobias Gruetzmacher [ tgr ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
