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

Want to know which user started a build that is sitting in the queue

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Server: Ubuntu 12.04 Server

      For a build that is sitting in the queue that was started by a user clicking the build button, it would be tremendously helpful to see the users name when I hover my mouse over that job in the queue. I envision something like what parameterized builds do (we see the parameter values when hovering over the job).

      For those builds initiated by an SCM commit(s), displaying the user(s) that committed the change that initiated the job would be very helpful.

      For those builds initiated by a timer, maybe "Initiated by timer" could be displayed.

      We'd want this information to help us to know who to contact if we need to re-prioritize or cancel jobs sitting in the queue.

      Since we use the build-user-vars plugin, we'd be happy if someone from this team implemented the functionality as well.

          [JENKINS-19250] Want to know which user started a build that is sitting in the queue

          Daniel Beck added a comment -

          Also, in case of "Started by SCM change", you can always access the project's SCM Polling Log to see what changed, then take a look. So I don't consider this critical.

          Daniel Beck added a comment - Also, in case of "Started by SCM change", you can always access the project's SCM Polling Log to see what changed, then take a look. So I don't consider this critical.

          Shannon Kerr added a comment -

          Got it. Thanks very much Daniel. I really appreciate this enhancement.

          Shannon Kerr added a comment - Got it. Thanks very much Daniel. I really appreciate this enhancement.

          Code changed in jenkins
          User: Daniel Beck
          Path:
          core/src/main/java/hudson/model/Queue.java
          core/src/main/resources/lib/hudson/queue.jelly
          http://jenkins-ci.org/commit/jenkins/19e40a9338a70dbf51f6236be7fcf2fc9b7fb511
          Log:
          [FIX JENKINS-19250] Add causes to queue item tool tip

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Queue.java core/src/main/resources/lib/hudson/queue.jelly http://jenkins-ci.org/commit/jenkins/19e40a9338a70dbf51f6236be7fcf2fc9b7fb511 Log: [FIX JENKINS-19250] Add causes to queue item tool tip

          Code changed in jenkins
          User: Daniel Beck
          Path:
          core/src/main/java/hudson/model/Queue.java
          core/src/main/resources/lib/hudson/queue.jelly
          http://jenkins-ci.org/commit/jenkins/b1520376340096fe47b19f5b906e275e42fb0a61
          Log:
          Merge pull request #1245 from daniel-beck/JENKINS-19250

          [FIX JENKINS-19250] Add causes to queue item tool tip

          Compare: https://github.com/jenkinsci/jenkins/compare/73c00442d24e...b15203763400

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Queue.java core/src/main/resources/lib/hudson/queue.jelly http://jenkins-ci.org/commit/jenkins/b1520376340096fe47b19f5b906e275e42fb0a61 Log: Merge pull request #1245 from daniel-beck/ JENKINS-19250 [FIX JENKINS-19250] Add causes to queue item tool tip Compare: https://github.com/jenkinsci/jenkins/compare/73c00442d24e...b15203763400

          dogfood added a comment -

          Integrated in jenkins_main_trunk #3422
          [FIX JENKINS-19250] Add causes to queue item tool tip (Revision 19e40a9338a70dbf51f6236be7fcf2fc9b7fb511)

          Result = SUCCESS
          daniel-beck : 19e40a9338a70dbf51f6236be7fcf2fc9b7fb511
          Files :

          • core/src/main/resources/lib/hudson/queue.jelly
          • core/src/main/java/hudson/model/Queue.java

          dogfood added a comment - Integrated in jenkins_main_trunk #3422 [FIX JENKINS-19250] Add causes to queue item tool tip (Revision 19e40a9338a70dbf51f6236be7fcf2fc9b7fb511) Result = SUCCESS daniel-beck : 19e40a9338a70dbf51f6236be7fcf2fc9b7fb511 Files : core/src/main/resources/lib/hudson/queue.jelly core/src/main/java/hudson/model/Queue.java

          Shannon Kerr added a comment -

          Looks good (testing the latest weekly). Couple of notes:

          1. When I go to the project page and see a job waiting in the queue, I do not see the "Started by" reason.
          2. When I am on the Jenkins main page and I hover over a job in the queue when the server is waiting to shutdown, the "Started By" value is above the "Jenkins is about to shutdown", separate from the rest of the configuration.

          No big problems and maybe you intended for things to be this way, but thought I'd mention.

          Thanks!

          Shannon Kerr added a comment - Looks good (testing the latest weekly). Couple of notes: 1. When I go to the project page and see a job waiting in the queue, I do not see the "Started by" reason. 2. When I am on the Jenkins main page and I hover over a job in the queue when the server is waiting to shutdown, the "Started By" value is above the "Jenkins is about to shutdown", separate from the rest of the configuration. No big problems and maybe you intended for things to be this way, but thought I'd mention. Thanks!

          Daniel Beck added a comment -

          Fixed in 1.567.

          Daniel Beck added a comment - Fixed in 1.567.

          Daniel Beck added a comment - - edited

          Shannon:

          Re 1: Will investigate. One problem is it's not rendered in a tooltip, so I'd have to account for multiple build causes and trim the list. So I just didn't bother so far
          Re 2: Please be more specific what you mean 'separate from the rest of the configuration'. Build causes are first, followed by the cause of blockage (Jenkins shutting down for example, or a required node offline), followed by the age.

          Daniel Beck added a comment - - edited Shannon: Re 1: Will investigate. One problem is it's not rendered in a tooltip, so I'd have to account for multiple build causes and trim the list. So I just didn't bother so far Re 2: Please be more specific what you mean 'separate from the rest of the configuration'. Build causes are first, followed by the cause of blockage (Jenkins shutting down for example, or a required node offline), followed by the age.

          Shannon Kerr added a comment -

          OK on 1.

          For 2, I see something structured like (I'm numbering the lines):
          1. Started by Shannon Kerr
          2. Jenkins is about to shutdown
          3. The rest of the parameters for that build (e.g. svn branch etc)

          I thought that 1 would have been kept with 3 and 2 would have been above them both. I considered the person who started the build part of the build parameters, but now that I think about it I could see how others may not think that way. I'll leave it up to you.

          I really appreciate your responsiveness during the work on this ticket. Thanks very much.

          Shannon Kerr added a comment - OK on 1. For 2, I see something structured like (I'm numbering the lines): 1. Started by Shannon Kerr 2. Jenkins is about to shutdown 3. The rest of the parameters for that build (e.g. svn branch etc) I thought that 1 would have been kept with 3 and 2 would have been above them both. I considered the person who started the build part of the build parameters, but now that I think about it I could see how others may not think that way. I'll leave it up to you. I really appreciate your responsiveness during the work on this ticket. Thanks very much.

          Shannon Kerr added a comment -

          btw, the Jenkins Trac plugin that we use in our issue tracker (in the "timeline") is able to list those who triggered the build if the build was triggered by a commit. So, it looks like there may be code out there that could be reused to list anyone responsible for triggering a build. Of course, that list could be large. I think you pointed this out earlier.

          Shannon Kerr added a comment - btw, the Jenkins Trac plugin that we use in our issue tracker (in the "timeline") is able to list those who triggered the build if the build was triggered by a commit. So, it looks like there may be code out there that could be reused to list anyone responsible for triggering a build. Of course, that list could be large. I think you pointed this out earlier.

            danielbeck Daniel Beck
            kerrhome Shannon Kerr
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: