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

Ability to move job to top of queue

    Details

    • Type: Improvement
    • Status: Reopened
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: other
    • Labels:
      None
    • Environment:
      Platform: PC, OS: Windows 2000
    • Similar Issues:

      Description

      If you have a large number of jobs queued up waiting for an executor, it would
      be helpful if there were a means of moving a job to the front of the queue.
      Perhaps a button next to the "cancel" button with an up arrow.

      This button should only appear if there are more jobs than executors, and only
      for users with either the Admin privilege, or the Job|Build privilege.

        Attachments

          Issue Links

            Activity

            frizbog frizbog created issue -
            Hide
            frizbog frizbog added a comment -

            I'm thinking that adding a "priority" attribute to
            hudson.model.Queue.WaitingItem would be a good way to deal with this. The
            comparator could look at priority before looking at timestamp. Priority could
            be "Held", "Low", "Normal", and "High" and default to "Normal". Various
            functions could increase or decrease the priority of a job.

            Show
            frizbog frizbog added a comment - I'm thinking that adding a "priority" attribute to hudson.model.Queue.WaitingItem would be a good way to deal with this. The comparator could look at priority before looking at timestamp. Priority could be "Held", "Low", "Normal", and "High" and default to "Normal". Various functions could increase or decrease the priority of a job.
            Hide
            frizbog frizbog added a comment -

            I'm going to try doing this.

            Show
            frizbog frizbog added a comment - I'm going to try doing this.
            Hide
            kohsuke Kohsuke Kawaguchi added a comment -

            If you do this, I'd encourage you to use AJAX D&D reordering, as opposed to
            additional button.

            Given the relative unimportance of the feature (sorry), it would be better not
            to clutter the UI.

            If you have a large number of queued up jobs, you really should just add more
            slaves.

            Show
            kohsuke Kohsuke Kawaguchi added a comment - If you do this, I'd encourage you to use AJAX D&D reordering, as opposed to additional button. Given the relative unimportance of the feature (sorry), it would be better not to clutter the UI. If you have a large number of queued up jobs, you really should just add more slaves.
            Hide
            frizbog frizbog added a comment -

            Based on the recent discussion of swappable queue implementations, etc., I'm
            going to put this back to be worked on later in a more coordinated effort.

            Show
            frizbog frizbog added a comment - Based on the recent discussion of swappable queue implementations, etc., I'm going to put this back to be worked on later in a more coordinated effort.
            mdonohue mdonohue made changes -
            Field Original Value New Value
            Link This issue depends on JENKINS-2072 [ JENKINS-2072 ]
            Hide
            javadude Carl Quinn added a comment -

            Throwing in my $.02: We have a case where most of the time we have plenty of executors, but every few days we integrate changes to the build tools in the source repo, usually after hours, and the result is that nearly everything rebuilds. So this takes a couple of hours, and occasionally someone needs to get a build triggered and through the system when this is happening. Being able to expedite a particular build would be handy.

            I think the priority plugin has the potential to fix this: http://issues.jenkins-ci.org/browse/JENKINS-8275 , but I thought I'd chime in here too.

            Show
            javadude Carl Quinn added a comment - Throwing in my $.02: We have a case where most of the time we have plenty of executors, but every few days we integrate changes to the build tools in the source repo, usually after hours, and the result is that nearly everything rebuilds. So this takes a couple of hours, and occasionally someone needs to get a build triggered and through the system when this is happening. Being able to expedite a particular build would be handy. I think the priority plugin has the potential to fix this: http://issues.jenkins-ci.org/browse/JENKINS-8275 , but I thought I'd chime in here too.
            Hide
            btb3 Martin Ba added a comment -

            I'll put a comment here instead of creating a new issue or renaming this one right away, but shouldn't this really read: "Allow for rearranging / editing the build queue"? (Note: I've not found any other current issue than this one here.)

            That is – and I think this is an extremely "natural" requirement for people who's build queue is full regularly – what we need is for the build queue to be "editable": Move waiting jobs around arbitrarily. (And I think the Priority Sorter Plugin should only determine the inital sort order.)

            Show
            btb3 Martin Ba added a comment - I'll put a comment here instead of creating a new issue or renaming this one right away, but shouldn't this really read: "Allow for rearranging / editing the build queue"? (Note: I've not found any other current issue than this one here.) That is – and I think this is an extremely "natural" requirement for people who's build queue is full regularly – what we need is for the build queue to be "editable": Move waiting jobs around arbitrarily. (And I think the Priority Sorter Plugin should only determine the inital sort order.)
            Hide
            frahi Franz Hirschbeck added a comment -

            This feature would be very helpful for our scenario. It is really annoying if one has to either wait for other projects to be build first or need to stop them and thus breaking the usual code checking functionality of the build server.

            There are some situations like developing/debugging the build of the server itself or using the artifacts of the project as an urgent release where this feature would be really nice.

            Adding more slaves is reducing the problem but not really solving (at least for numSlaves < numProjects).

            Show
            frahi Franz Hirschbeck added a comment - This feature would be very helpful for our scenario. It is really annoying if one has to either wait for other projects to be build first or need to stop them and thus breaking the usual code checking functionality of the build server. There are some situations like developing/debugging the build of the server itself or using the artifacts of the project as an urgent release where this feature would be really nice. Adding more slaves is reducing the problem but not really solving (at least for numSlaves < numProjects).
            Hide
            evernat evernat added a comment -

            I think that this feature request is now in the Accelerated Build Now plugin, which is available in your Jenkins update center.

            The plugin's page is at:
            https://wiki.jenkins-ci.org/display/JENKINS/Accelerated+Build+Now+Plugin

            Show
            evernat evernat added a comment - I think that this feature request is now in the Accelerated Build Now plugin, which is available in your Jenkins update center. The plugin's page is at: https://wiki.jenkins-ci.org/display/JENKINS/Accelerated+Build+Now+Plugin
            evernat evernat made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 131951 ] JNJira + In-Review [ 186490 ]
            Hide
            euphxenos Andrew Lawrence added a comment -

            The Accelerated Build Now plugin doesn't fully address the problem. It can't help you if you want to increase the priority of a job that was queued noninteractively (and can't easily be started manually). Usually when we want to have a job jump to the head of the queue it's a job that was queued by the Gerrit Trigger Plugin, and there's no way to trigger one of those with Accelerated Build Now. Just adding more slaves would be great, but each of the slaves in this case represents a very expensive set of test hardware. Being able to bump an existing job to the head of the queue is still a missing and needed feature.

            Show
            euphxenos Andrew Lawrence added a comment - The Accelerated Build Now plugin doesn't fully address the problem. It can't help you if you want to increase the priority of a job that was queued noninteractively (and can't easily be started manually). Usually when we want to have a job jump to the head of the queue it's a job that was queued by the Gerrit Trigger Plugin, and there's no way to trigger one of those with Accelerated Build Now. Just adding more slaves would be great, but each of the slaves in this case represents a very expensive set of test hardware. Being able to bump an existing job to the head of the queue is still a missing and needed feature.
            euphxenos Andrew Lawrence made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]

              People

              • Assignee:
                Unassigned
                Reporter:
                frizbog frizbog
              • Votes:
                32 Vote for this issue
                Watchers:
                29 Start watching this issue

                Dates

                • Created:
                  Updated: