Status: Resolved (View Workflow)
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
Tobias Gruetzmacher added a comment -
This is now fixed (for better or worse) in 2.6 - I didn't think about the information disclosure issue, will discuss with contributors...
Tobias Gruetzmacher added a comment - This is now fixed (for better or worse) in 2.6 - I didn't think about the information disclosure issue, will discuss with contributors...
This could cause a security issue: users would be able to know about Job names which they do not have read/discover permission on. That's why current locks status is shown to admins only in a separated page.