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

Expanding collapsed steps on a failed Pipeline run causes the view port to scroll to the bottom of the page

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • blueocean-plugin
    • None

      Scope
      Expanding any step should scroll to the bottom of the expanded step

      Problem
      Video

      Take this Pipeline run for example. When navigating to the page, the view port predictably/correctly scrolls to the bottom, to show the tail end of the failed step

      When the user scrolls up to the top of the page and clicks/expands a step which succeeded, and has Console Output (e.g. "General SCM" in this Pipeline run), the step's Console Output loads, and then the view port returns to the absolute bottom of the page.

      This is extremely annoying and makes getting additional information about failed Pipeline runs much more tedious than it should be.

          [JENKINS-45408] Expanding collapsed steps on a failed Pipeline run causes the view port to scroll to the bottom of the page

          Liam Newman added a comment -

          I get this same result. I'm using Chrome and Blue Ocean 1.1.2.

          Liam Newman added a comment - I get this same result. I'm using Chrome and Blue Ocean 1.1.2.

          macetw added a comment - - edited

          I think the problem is larger than this.

          On a running build, where the console is updating, the browser always scrolls to the bottom. What if I'm looking at my pipeline view at the top? Well, if consoles are open (which they are by default), the scroll keeps pushing to the bottom.

          The workaround is to scroll to the top, and be fast enough to collapse the console view of the given step that is running. Quick, now! OH you missed it - a refresh happened. Try it again. This wastes SO MUCH of my time and really causes stress.

          This might be most obvious for jobs that have many tasks done in parallel, where the pipeline view is more important. I'd like to ensure I can monitor more than one task, and each task has console updates going on. I want to observe if other tasks fail or pass or are waiting to start.

          macetw added a comment - - edited I think the problem is larger than this. On a running build, where the console is updating, the browser always scrolls to the bottom. What if I'm looking at my pipeline view at the top? Well, if consoles are open (which they are by default), the scroll keeps pushing to the bottom. The workaround is to scroll to the top, and be fast enough to collapse the console view of the given step that is running. Quick, now! OH you missed it - a refresh happened. Try it again. This wastes SO MUCH of my time and really causes stress. This might be most obvious for jobs that have many tasks done in parallel, where the pipeline view is more important. I'd like to ensure I can monitor more than one task, and each task has console updates going on. I want to observe if other tasks fail or pass or are waiting to start.

            Unassigned Unassigned
            rtyler R. Tyler Croy
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: