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

cannot stop auto-scrolling in blue ocean console

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • blueocean-plugin
    • None
    • 1.10.2

      When I have console for an active stage open, I see the new messages added real-time to the bottom of the console window, so far so good.

      But if I want to scroll up to see messages printed a couple seconds ago, or scroll up so I can collapse the console window so I can view the pipeline, I'm prevented from doing so because every new log message forces the focus back down to the bottom. In legacy Jenkins, being at the bottom of the window would continue to update, but if the user scrolled up away from the bottom, it would not force focus back down to the bottom with every new message.

      When the messages come quickly, I'm forced to spam the 'home' key on the keyboard to try and jump up to the top and click the 'collapse' icon as quickly as possible, but not usually not quick enough. There should be some standardized way of preventing the auto scroll.

          [JENKINS-55849] cannot stop auto-scrolling in blue ocean console

          boris ivan created issue -

          Pete Moore added a comment -

          I found this maybe a learning experience rather than a bug.  The auto tail will happen if you click on the stage node again and open the text box. To stop it auto scrolling you use the scroll bar.  What is annoying is auto open because if another stage completes, it seems to open that one in your view.  This happens on parallel steps.

          Pete Moore added a comment - I found this maybe a learning experience rather than a bug.  The auto tail will happen if you click on the stage node again and open the text box. To stop it auto scrolling you use the scroll bar.  What is annoying is auto open because if another stage completes, it seems to open that one in your view.  This happens on parallel steps.

          boris ivan added a comment -

          Hi pete312 – for me, using the scroll bar doesn't work, though I found that if I use the mouse wheel first, it works.

          Specifically: assuming I've clicked on an active stage, then opened the text box for the step that's active, it will auto scroll and keep focus at the bottom. At that point, if I do nothing other than attempt to use the scroll bar to bring the pipeline back into view (i.e. at the top of the browser window that was otherwise scrolled out of view because of all the text in the text box) – as soon as I release the scroll bar, it would jump back down to the bottom of the text window, as soon as the next log message was printed.

          But what I've found since then, is that while I'm at the bottom of the active text box – if I use the middle mouse button to scroll up a few lines, that 'breaks' the connection such that I can subsequently use the scroll bar controls, or continue to use the middle mouse button, or anything, and it won't auto-jump back down to the bottom of the text window when the next log message appears.

          But without using that middle mouse button first, using the scroll bar controls would allow me to move up.... but as soon as I let go, it jumped back down.

          boris ivan added a comment - Hi pete312 – for me, using the scroll bar doesn't work, though I found that if I use the mouse wheel first, it works. Specifically: assuming I've clicked on an active stage, then opened the text box for the step that's active, it will auto scroll and keep focus at the bottom. At that point, if I do nothing other than attempt to use the scroll bar to bring the pipeline back into view (i.e. at the top of the browser window that was otherwise scrolled out of view because of all the text in the text box) – as soon as I release the scroll bar, it would jump back down to the bottom of the text window, as soon as the next log message was printed. But what I've found since then, is that while I'm at the bottom of the active text box – if I use the middle mouse button to scroll up a few lines, that 'breaks' the connection such that I can subsequently use the scroll bar controls, or continue to use the middle mouse button, or anything, and it won't auto-jump back down to the bottom of the text window when the next log message appears. But without using that middle mouse button first, using the scroll bar controls would allow me to move up.... but as soon as I let go, it jumped back down.

          Micah Snyder added a comment -

          Auto-scrolling and auto-open when a stage completes is tremendously annoying when viewing a larger pipeline with many parallel stages.  Any change in status to one stage scrolls me to the bottom of the screen.

          Micah Snyder added a comment - Auto-scrolling and auto-open when a stage completes is tremendously annoying when viewing a larger pipeline with many parallel stages.  Any change in status to one stage scrolls me to the bottom of the screen.

          David Resnick added a comment -

          This issue causes me to navigate away from Blue Ocean 90% of the time. And the issue itself makes it hard to reach the link that will take me to the standard view of the build I'm in.

          David Resnick added a comment - This issue causes me to navigate away from Blue Ocean 90% of the time. And the issue itself makes it hard to reach the link that will take me to the standard view of the build I'm in.

          Erik Zenker added a comment -

          Blue ocean is not usable at all with this bug! I am trying to have a detailed look at the ci log in blue ocean but every  now and then it scrolls to the bottom. Travis CI has a button for that which toggles autoscrolling.

          Erik Zenker added a comment - Blue ocean is not usable at all with this bug! I am trying to have a detailed look at the ci log in blue ocean but every  now and then it scrolls to the bottom. Travis CI has a button for that which toggles autoscrolling.

          I signed up for an account just to upvote this issue. The most annoying part for me is that, even after my build is totally complete, it keeps trying to auto scroll! My build has already failed, I'm just trying to read through the error logs, and it keeps scrolling back to the bottom of the page. Incredibly frustrating.

          Gabriel Gilder added a comment - I signed up for an account just to upvote this issue. The most annoying part for me is that, even after my build is totally complete, it keeps trying to auto scroll! My build has already failed, I'm just trying to read through the error logs, and it keeps scrolling back to the bottom of the page. Incredibly frustrating.

          I believe the latest version of Blue Ocean has solved this issue, where it pins the current step to the top of the browser, so you can always click it and it will collapse the step. 

          Dimitar Patroev added a comment - I believe the latest version of Blue Ocean has solved this issue, where it pins the current step to the top of the browser, so you can always click it and it will collapse the step. 

          David added a comment -

          dpatroev this isn't just about being able to collapse the log.  When a build is complete (failed) and I'm reading through the logs of the failed step, every few seconds Blue Ocean will still autoscroll to the bottom of the log.

          Given the reason for a failure isn't necessarily at the bottom of the log (e.g., could be a test failure early in a large suite of tests) it's extremely frustrating and essentially unusable, as I keep getting interrupted when trying to read what has gone wrong.

          David added a comment - dpatroev  this isn't just about being able to collapse the log.  When a build is complete (failed) and I'm reading through the logs of the failed step, every few seconds Blue Ocean will still autoscroll to the bottom of the log. Given the reason for a failure isn't necessarily at the bottom of the log (e.g., could be a test failure early in a large suite of tests) it's  extremely frustrating and essentially unusable, as I keep getting interrupted when trying to read what has gone wrong.

          Rok Cvahte added a comment - - edited

          I agree with daiscog here. The way it is currently implemented makes it very difficult to read the error without being interrupted by jumps up&down.

          • We are often having to resort to reading console output (text). Which is a shame, because it's not as nicely structured as the BlueOcean view.
          • Would be really nice to have an option to disable this automatic scroll feature.

          Rok Cvahte added a comment - - edited I agree with daiscog here. The way it is currently implemented makes it very difficult to read the error without being interrupted by jumps up&down. We are often having to resort to reading console output (text). Which is a shame, because it's not as nicely structured as the BlueOcean view. Would be really nice to have an option to disable this automatic scroll feature.

            Unassigned Unassigned
            borisivan boris ivan
            Votes:
            21 Vote for this issue
            Watchers:
            26 Start watching this issue

              Created:
              Updated: