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

          Shannon Kerr created issue -
          Daniel Beck made changes -
          Assignee New: Daniel Beck [ danielbeck ]
          Daniel Beck made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Daniel Beck added a comment -

          https://github.com/jenkinsci/jenkins/pull/1245

          Doesn't show SCM details, only that it was an SCM change. Still, should suffice for 90% of the questions (especially to distinguish manually started from trigger-started builds).

          Daniel Beck added a comment - https://github.com/jenkinsci/jenkins/pull/1245 Doesn't show SCM details, only that it was an SCM change. Still, should suffice for 90% of the questions (especially to distinguish manually started from trigger-started builds).

          Shannon Kerr added a comment -

          Sounds good. For the other 10%, you could just default to "SCMTrigger" like the "User Build Vars" plugin does. Then it would show up at least as Scm triggered in the queue.

          Shannon Kerr added a comment - Sounds good. For the other 10%, you could just default to "SCMTrigger" like the "User Build Vars" plugin does. Then it would show up at least as Scm triggered in the queue.

          Shannon Kerr added a comment -

          Of course eventually showing the account(s)/user(s) that triggered the build would be great, but I'll take what I can get.

          Shannon Kerr added a comment - Of course eventually showing the account(s)/user(s) that triggered the build would be great, but I'll take what I can get.

          Daniel Beck added a comment -

          That's what I meant by 90%: I'm showing the same text as shows up (most of the time) on build pages. Since it only says "Started by an SCM change" (i.e. no user(s)), that's what I'm doing as well.

          Some English localization text samples:

          Started by command line by {0}
          Started by an SCM change
          Started by timer
          Legacy code started this job.  No cause information is available
          Started by upstream project "{0}" build number {1}
          Started by user {0}
          Started by user {0}
          Started by remote host {0}
          Started by remote host {0} with note: {1}

          Problem with SCM change is also that it can be an arbitrary number of commits by as many users if you're polling (and that rarely).

          Daniel Beck added a comment - That's what I meant by 90%: I'm showing the same text as shows up (most of the time) on build pages. Since it only says "Started by an SCM change" (i.e. no user(s)), that's what I'm doing as well. Some English localization text samples: Started by command line by {0} Started by an SCM change Started by timer Legacy code started this job. No cause information is available Started by upstream project "{0}" build number {1} Started by user {0} Started by user {0} Started by remote host {0} Started by remote host {0} with note: {1} Problem with SCM change is also that it can be an arbitrary number of commits by as many users if you're polling (and that rarely).

          Daniel Beck added a comment -

          Unrelated to build-user-var

          Daniel Beck added a comment - Unrelated to build-user-var
          Daniel Beck made changes -
          Component/s Original: build-user-vars [ 17477 ]

          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.

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

              Created:
              Updated:
              Resolved: