Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-50618

Provide information in the console about who owns a lock when waiting

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Issue Links

            Activity

            allan_burdajewicz Allan BURDAJEWICZ created issue -
            Hide
            amuniz Antonio Muñiz added a comment - - edited

            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.

            Show
            amuniz Antonio Muñiz added a comment - - edited 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.
            jamesdumay James Dumay made changes -
            Field Original Value New Value
            Remote Link This issue links to "CloudBees Internal CD-458 (Web Link)" [ 20539 ]
            Hide
            tgr 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...

            Show
            tgr 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...
            tgr Tobias Gruetzmacher made changes -
            Released As https://github.com/jenkinsci/lockable-resources-plugin/releases/tag/lockable-resources-2.6
            Assignee Tobias Gruetzmacher [ tgr ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]

              People

              Assignee:
              tgr Tobias Gruetzmacher
              Reporter:
              allan_burdajewicz Allan BURDAJEWICZ
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: