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

Split build queue into three: Waiting, Blocked, Scheduled

    • Icon: Patch Patch
    • Resolution: Incomplete
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: All

      I found from looking at the buildque it is very hard to say which build will be
      scheduled next. Hudson maintains three queues: On for Items that can actually be
      builed, one for items within ther quiete period and on for blocked items.
      I wrote a patch to reflect this in the gui.

          [JENKINS-1917] Split build queue into three: Waiting, Blocked, Scheduled

          martinficker added a comment -

          Created an attachment (id=293)
          A Screenshot of how the buildqueue looks in the patched version

          martinficker added a comment - Created an attachment (id=293) A Screenshot of how the buildqueue looks in the patched version

          martinficker added a comment -

          Please comment if you woul'd like to have this changed in the core.

          martinficker added a comment - Please comment if you woul'd like to have this changed in the core.

          I think it's not obvious to users what those three classification means.

          This information is today provided in the tooltip. Did you feel that that was
          not sufficient? What's the motivation for this change? Why did you want to be
          able to tell which build gets scheduled next?

          Also note that the order of items shown in the build queue should have been the
          same before and after your change — perhaps if we show the blocked jobs in red
          or yellow, does that help you make a distinction?

          Kohsuke Kawaguchi added a comment - I think it's not obvious to users what those three classification means. This information is today provided in the tooltip. Did you feel that that was not sufficient? What's the motivation for this change? Why did you want to be able to tell which build gets scheduled next? Also note that the order of items shown in the build queue should have been the same before and after your change — perhaps if we show the blocked jobs in red or yellow, does that help you make a distinction?

          martinficker added a comment -

          We do often have many builds in the queue (>50). The Tooltips can provide
          information for a single build but don't give an overview.
          Developers look for their build to guess when it's done (For example to tell QS
          they could pull off a new version). What they see currently: Their build is
          displayed a the top of the list first (Because it's waiting, but they don't
          know...). After a short time the build seems to fall back to the end of the
          queue. When Blocking comes into play (as it does with another patch I'm
          currently trying) the behaviour becomes even less understandable.
          Showing the items in different colors looks like a good solution to me.
          Additionally I would vote for a change in order:

          BuildableItems
          WaitingItems, shortes time first
          BlockedItems

          This way the top Item will very likely be the next to be build.

          martinficker added a comment - We do often have many builds in the queue (>50). The Tooltips can provide information for a single build but don't give an overview. Developers look for their build to guess when it's done (For example to tell QS they could pull off a new version). What they see currently: Their build is displayed a the top of the list first (Because it's waiting, but they don't know...). After a short time the build seems to fall back to the end of the queue. When Blocking comes into play (as it does with another patch I'm currently trying) the behaviour becomes even less understandable. Showing the items in different colors looks like a good solution to me. Additionally I would vote for a change in order: BuildableItems WaitingItems, shortes time first BlockedItems This way the top Item will very likely be the next to be build.

          mdonohue added a comment -

          Cleaning up the summary

          mdonohue added a comment - Cleaning up the summary

          mdonohue added a comment -
              • Issue 2029 has been marked as a duplicate of this issue. ***

          mdonohue added a comment - Issue 2029 has been marked as a duplicate of this issue. ***

          Daniel Beck added a comment -

          Patch seems to have been disappeared (and wouldn't merge anymore anyway, so resolving as Incomplete).

          Daniel Beck added a comment - Patch seems to have been disappeared (and wouldn't merge anymore anyway, so resolving as Incomplete).

            Unassigned Unassigned
            martinficker martinficker
            Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: