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

Add Build Now and Configure Project links to all pages within a job

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • None
    • All

      When I am trying to debug getting a build up and going 99% of the time when I am looking at the console output for a build the next action I want to take is either change the settings for the build or start a new build. It is very annoying that to do either of them you have to go back to the project to get the links to do these actions.

      I realize that these actions are not actions associated with the console output itself, but it would sure be convenient to be able to do these actions from any page under that job.

      Might also be helpful to include the workspace link, but that may be too confusing as you might be looking at the console output for an older build and the current workspace does not correspond to what it was for the build. Would be cool if workspace link were shown only on output screen of latest build to reduce this confusion.

          [JENKINS-19899] Add Build Now and Configure Project links to all pages within a job

          Oleg Nenashev added a comment -

          In general... you could use "Rebuild Plugin" or pop-ups on the upper tab bar.
          If you experience issues with actions provided by plugins, please open issues to them. Sidepanels are being defined by actions, hence it is not possible to force links you request on All pages

          Oleg Nenashev added a comment - In general... you could use "Rebuild Plugin" or pop-ups on the upper tab bar. If you experience issues with actions provided by plugins, please open issues to them. Sidepanels are being defined by actions, hence it is not possible to force links you request on All pages

          Daniel Beck added a comment -

          As these are actions on a different object (project rather than build) these wouldn't make much sense to be honest, and they're easy enough to reach using the bread crumb bar's context menu. Tempted to resolve as Won't Fix – any opposing views?

          Daniel Beck added a comment - As these are actions on a different object (project rather than build) these wouldn't make much sense to be honest, and they're easy enough to reach using the bread crumb bar's context menu. Tempted to resolve as Won't Fix – any opposing views?

          Dale King added a comment - - edited

          Yes, Daniel I am aware of the faulty logic underlying the decision to not put these links on sub pages of the job, but restating that faulty logic does not make it valid. They are not completely different objects, they are sub objects of each other. Sure there should be some differentiation in the links between the actions to take at the job level and the sub page level but that does not justify removing the job level links. And no, having to do target practice to hit that tiny little triangle to open up a submenu to then see the actions and click yet again is not good enough.

          Any level of usability testing would show that Build Now and Configure are the most often used actions taken on any job, followed by see the console of the latest build. Luckily we have plugins like extra columns which lets up put those actions directly on the dashboard but navigating within a job to these actions is still a pain.

          Dale King added a comment - - edited Yes, Daniel I am aware of the faulty logic underlying the decision to not put these links on sub pages of the job, but restating that faulty logic does not make it valid. They are not completely different objects, they are sub objects of each other. Sure there should be some differentiation in the links between the actions to take at the job level and the sub page level but that does not justify removing the job level links. And no, having to do target practice to hit that tiny little triangle to open up a submenu to then see the actions and click yet again is not good enough. Any level of usability testing would show that Build Now and Configure are the most often used actions taken on any job, followed by see the console of the latest build. Luckily we have plugins like extra columns which lets up put those actions directly on the dashboard but navigating within a job to these actions is still a pain.

          Daniel Beck added a comment -

          faulty logic

          That's a nice claim, but nothing you write actually shows it's wrong. You wouldn't add 'Manage Jenkins' or 'Edit View' to a build, just because they're (great) grand children of the respective View and Jenkins objects, would you?


          Where I was imprecise (and may have misunderstood your request) is that I'm referring to the side panel, which contains actions related to the current object. It makes no sense to put these there, because you're not building or configuring an existing build.

          Options I could think of which keep the side panel clean and still make these easier to reach:

          • Sectioned side panel which would make it clear that these belong to a different object. E.g. as sub-items of 'Back to Project' which could get a different label (e.g. named after the project)
          • Adding icon links to (a possible bigger) bread crumb bar, e.g. build action icon next to the context menu triangle. This would clearly associate the action with the object it's related to.

          Daniel Beck added a comment - faulty logic That's a nice claim, but nothing you write actually shows it's wrong. You wouldn't add 'Manage Jenkins' or 'Edit View' to a build, just because they're (great) grand children of the respective View and Jenkins objects, would you? Where I was imprecise (and may have misunderstood your request) is that I'm referring to the side panel, which contains actions related to the current object. It makes no sense to put these there, because you're not building or configuring an existing build. Options I could think of which keep the side panel clean and still make these easier to reach: Sectioned side panel which would make it clear that these belong to a different object. E.g. as sub-items of 'Back to Project' which could get a different label (e.g. named after the project) Adding icon links to (a possible bigger) bread crumb bar, e.g. build action icon next to the context menu triangle. This would clearly associate the action with the object it's related to.

            Unassigned Unassigned
            dalewking Dale King
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: