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

Difficult to determine parameters of queue items

      The parameters of queued builds are only visible in the tooltips of entries from the build queue on the Jenkins index page, not in the build history widget of the individual jobs. This makes it difficult to tell what parameterized builds are going to be run.

      Also the existing tooltips show internal class names suitable for a debugger, rather than a proper human-friendly display.

          [JENKINS-17454] Difficult to determine parameters of queue items

          dogfood added a comment -

          Integrated in jenkins_main_trunk #2431
          [FIXED JENKINS-17454] Display parameters of queue items in build history widget. (Revision 750da1a7c0700655129d594d56bfc41214891e50)

          Result = SUCCESS
          Jesse Glick : 750da1a7c0700655129d594d56bfc41214891e50
          Files :

          • core/src/main/java/hudson/model/FileParameterValue.java
          • core/src/main/resources/lib/hudson/queue.jelly
          • core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly
          • changelog.html
          • core/src/main/java/hudson/model/PasswordParameterValue.java
          • core/src/main/java/hudson/model/StringParameterValue.java
          • core/src/main/java/hudson/model/BooleanParameterValue.java
          • core/src/main/java/hudson/model/JobParameterValue.java
          • core/src/main/java/hudson/model/RunParameterValue.java

          dogfood added a comment - Integrated in jenkins_main_trunk #2431 [FIXED JENKINS-17454] Display parameters of queue items in build history widget. (Revision 750da1a7c0700655129d594d56bfc41214891e50) Result = SUCCESS Jesse Glick : 750da1a7c0700655129d594d56bfc41214891e50 Files : core/src/main/java/hudson/model/FileParameterValue.java core/src/main/resources/lib/hudson/queue.jelly core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly changelog.html core/src/main/java/hudson/model/PasswordParameterValue.java core/src/main/java/hudson/model/StringParameterValue.java core/src/main/java/hudson/model/BooleanParameterValue.java core/src/main/java/hudson/model/JobParameterValue.java core/src/main/java/hudson/model/RunParameterValue.java

          Code changed in jenkins
          User: Jesse Glick
          Path:
          changelog.html
          core/src/main/java/hudson/model/BooleanParameterValue.java
          core/src/main/java/hudson/model/FileParameterValue.java
          core/src/main/java/hudson/model/JobParameterValue.java
          core/src/main/java/hudson/model/PasswordParameterValue.java
          core/src/main/java/hudson/model/RunParameterValue.java
          core/src/main/java/hudson/model/StringParameterValue.java
          core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly
          core/src/main/resources/lib/hudson/queue.jelly
          http://jenkins-ci.org/commit/jenkins/750da1a7c0700655129d594d56bfc41214891e50
          Log:
          [FIXED JENKINS-17454] Display parameters of queue items in build history widget.
          Also provide proper overrides of ParameterValue.getShortDescription, rather than delegating to toString.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/BooleanParameterValue.java core/src/main/java/hudson/model/FileParameterValue.java core/src/main/java/hudson/model/JobParameterValue.java core/src/main/java/hudson/model/PasswordParameterValue.java core/src/main/java/hudson/model/RunParameterValue.java core/src/main/java/hudson/model/StringParameterValue.java core/src/main/resources/hudson/widgets/BuildHistoryWidget/entries.jelly core/src/main/resources/lib/hudson/queue.jelly http://jenkins-ci.org/commit/jenkins/750da1a7c0700655129d594d56bfc41214891e50 Log: [FIXED JENKINS-17454] Display parameters of queue items in build history widget. Also provide proper overrides of ParameterValue.getShortDescription, rather than delegating to toString.

          Looks like the parameters for queued jobs are in the reverse order compared to the jobs? Quite a big usability bug if I'm not mistaking.

          Martin Wiklundh added a comment - Looks like the parameters for queued jobs are in the reverse order compared to the jobs? Quite a big usability bug if I'm not mistaking.

          Jesse Glick added a comment -

          @epkaxma can you clarify? The queue should be displayed starting with the newest entry, which would be the last to be sent to an executor (unless the scheduler blocks certain items etc.). The build history widget shows the predicted list of future jobs in the usual descending numeric order. Are you seeing something else?

          Jesse Glick added a comment - @epkaxma can you clarify? The queue should be displayed starting with the newest entry, which would be the last to be sent to an executor (unless the scheduler blocks certain items etc.). The build history widget shows the predicted list of future jobs in the usual descending numeric order. Are you seeing something else?

          Well, in the build history for my job I have the predicted list of build numbers in descending order on the left hand as usual. Last build in the queue on top. On the right hand I have the parameters in a readable format and the x button. But the parameter text blocks are in ascending order, first build in the queue on top.

          Martin Wiklundh added a comment - Well, in the build history for my job I have the predicted list of build numbers in descending order on the left hand as usual. Last build in the queue on top. On the right hand I have the parameters in a readable format and the x button. But the parameter text blocks are in ascending order, first build in the queue on top.

          Would be great if you could add the name of the user who started the job (when applicable) to the parameter text, now when you are improving this area.
          Something like (pending—Waiting for next available executor on MySlave, started by epkaxma)...

          Martin Wiklundh added a comment - Would be great if you could add the name of the user who started the job (when applicable) to the parameter text, now when you are improving this area. Something like (pending—Waiting for next available executor on MySlave, started by epkaxma)...

          Jesse Glick added a comment -

          Better to file follow-on issues (use JIRA’s link facility). Pull requests welcome, since I have no current plan to work further on this.

          Jesse Glick added a comment - Better to file follow-on issues (use JIRA’s link facility). Pull requests welcome, since I have no current plan to work further on this.

          You can use this plugin to show who trigger the build : https://wiki.jenkins-ci.org/display/JENKINS/Build+Trigger+Badge+Plugin

          Walter Kacynski added a comment - You can use this plugin to show who trigger the build : https://wiki.jenkins-ci.org/display/JENKINS/Build+Trigger+Badge+Plugin

          Roger Geere added a comment -

          We have gerrit triggered jobs. The gerrit trigger plugin converts the gerrit commit message (which may be very long) to Base64 and the above change makes the build queue display very messy as it tries to display the commit message on a single line.

          Roger Geere added a comment - We have gerrit triggered jobs. The gerrit trigger plugin converts the gerrit commit message (which may be very long) to Base64 and the above change makes the build queue display very messy as it tries to display the commit message on a single line.

          Jesse Glick added a comment -

          @rogerg please file related issues separately (using JIRA’s “blocking” links as needed).

          Jesse Glick added a comment - @rogerg please file related issues separately (using JIRA’s “blocking” links as needed).

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: