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

Pipeline view automatically scrolls down

    XMLWordPrintable

Details

    Description

      Hi, I'd like to display the picture (the SVG) of an ongoing pipeline in an html page that will display in a radiator. The problem I have is that when scripts (that are part of the pipeline execution) get executed the page scrolls down, hiding the picture. Would it be possible to add a no-scroll parameter to the url to disable the scrolling down of the page? Something like:

      http://server.com/blueocean/.../pipeline#no-scroll

      In other words, I want to always show in an unattended browser the picture attached (example).

      thanks!
      Gustavo.

      Attachments

        Activity

          kzantow Keith Zantow added a comment -

          jdumay I don't believe this is a duplicate of JENKINS-38226 - I think what gusgonnet72 is asking for is a way to display the executing pipeline of an individual job.

          kzantow Keith Zantow added a comment - jdumay I don't believe this is a duplicate of JENKINS-38226 - I think what gusgonnet72 is asking for is a way to display the executing pipeline of an individual job.
          jamesdumay James Dumay added a comment -

          Apologies, I marked this as the wrong duplicate - its JENKINS-41088. We are going to build a great page for a Pipeline that shows you the latest visualization of your Pipeline which will be perfect for big screens!

          jamesdumay James Dumay added a comment - Apologies, I marked this as the wrong duplicate - its JENKINS-41088 . We are going to build a great page for a Pipeline that shows you the latest visualization of your Pipeline which will be perfect for big screens!
          kzantow Keith Zantow added a comment -

          I still don't think this is the same. Someone may be interested in looking at ONE EXACT pipeline execution.

          kzantow Keith Zantow added a comment - I still don't think this is the same. Someone may be interested in looking at ONE EXACT pipeline execution.
          jamesdumay James Dumay added a comment -

          kzantow JENKINS-41088 is exactly the same as this feature request however there may be some details this ticket contributes that are not currently defined in it.

          jamesdumay James Dumay added a comment - kzantow JENKINS-41088 is exactly the same as this feature request however there may be some details this ticket contributes that are not currently defined in it.

          alright, thank you guys for the explanations.
          should I close this ticket?

          gusgonnet72 Gustavo Gonnet added a comment - alright, thank you guys for the explanations. should I close this ticket?
          jamesdumay James Dumay added a comment -

          gusgonnet72 ill do that now.

          jamesdumay James Dumay added a comment - gusgonnet72 ill do that now.
          jgamble Julian Gamble added a comment -

          jamesdumay Whilst I can agree that the ticket (JENKINS-41088) to create a dashboard view may address gusgonnet72's original ask, I don't think this ticket should be closed. It's still a completely valid user story to disable the auto-scroll functionality when viewing a pipeline as it can be jarring for users who don't typically consume log data first, but instead want to use the overview to drill down into failure areas they care about.

          jgamble Julian Gamble added a comment - jamesdumay Whilst I can agree that the ticket ( JENKINS-41088 ) to create a dashboard view may address gusgonnet72 's original ask, I don't think this ticket should be closed. It's still a completely valid user story to disable the auto-scroll functionality when viewing a pipeline as it can be jarring for users who don't typically consume log data first, but instead want to use the overview to drill down into failure areas they care about.
          jamesdumay James Dumay added a comment -

          jgamble the behaviour that you are describing is what the default is on master (1.4 release) right now.

          jamesdumay James Dumay added a comment - jgamble the behaviour that you are describing is what the default is on master (1.4 release) right now.

          jamesdumay hello  

          We are on Blue Ocean 1.4.1, on a red build I still get the auto-scrolled to the stage and step that has failed. I'd argue that the behaviour by default should be the same, just land the user on the pipeline overview (top of the page) and let them scroll to the failed step(s) themselves. 

          kordzik Dariusz Kordonski added a comment - jamesdumay hello   We are on Blue Ocean 1.4.1, on a red build I still get the auto-scrolled to the stage and step that has failed. I'd argue that the behaviour by default should be the same, just land the user on the pipeline overview (top of the page) and let them scroll to the failed step(s) themselves. 
          jamesdumay James Dumay added a comment - - edited

          kordzik yes, it automatically scrolls there on a failed run by design. I'd need to get some more feedback from users before we went ahead and changed this behaviour.

          Also, hello - great to see that you're a Blue Ocean user now

          jamesdumay James Dumay added a comment - - edited kordzik yes, it automatically scrolls there on a failed run by design. I'd need to get some more feedback from users before we went ahead and changed this behaviour. Also, hello - great to see that you're a Blue Ocean user now

          jamesdumay I would also support a change to where the top of the page is the default. I typically find myself scrolling up even in a failed build, just to see which part of the build that failed and then scrolling down to get the step log. 

          fkykko Staffan Forsell added a comment - jamesdumay I would also support a change to where the top of the page is the default. I typically find myself scrolling up even in a failed build, just to see which part of the build that failed and then scrolling down to get the step log. 
          stevedonie Steve Donie added a comment -

          jamesdumay please consider this as my vote as a user (as well as my whole team) to not automatically scroll.

          stevedonie Steve Donie added a comment - jamesdumay please consider this as my vote as a user (as well as my whole team) to not automatically scroll.
          jsnrth Jason R added a comment -

          jamesdumay ditto, my team and I would like to see this auto-scroll behavior disabled.

          We find ourselves scrolling back to the top nearly every time we navigate to a failed build from links on Github checks. Further, while the page is loading, the top with the pipeline and menu is shown – it only auto-scrolls to the bottom once the JS or whatever kicks in and loads the console output. This makes the UX disruptive as it jumps us away from where we were getting situated on the page.

          We would much prefer if the page did not assume we wanted to be at the bottom of the failed stage's console output, and instead allowed us to navigate where we want to go.

          I see that this issue is closed as a duplicate of JENKINS-41088, but I don't think that is quite the same request (per jgamble's comment about a year ago).

          We are running Blue Ocean 1.9.0.

          Thanks, -j

          jsnrth Jason R added a comment - jamesdumay  ditto, my team and I would like to see this auto-scroll behavior disabled. We find ourselves scrolling back to the top nearly every time we navigate to a failed build from links on Github checks. Further, while the page is loading, the top with the pipeline and menu is shown – it only auto-scrolls to the bottom once the JS or whatever kicks in and loads the console output. This makes the UX disruptive as it jumps us away from where we were getting situated on the page. We would much prefer if the page did not assume we wanted to be at the bottom of the failed stage's console output, and instead allowed us to navigate where we want to go. I see that this issue is closed as a duplicate of JENKINS-41088 , but I don't think that is quite the same request (per jgamble 's comment about a year ago). We are running Blue Ocean 1.9.0. Thanks, -j
          cetex oskar stenman added a comment -

          This is definitely not resolved, or handled by the referenced issue.

          Some builds we run ends up launching 15 parallel tasks (building AMI's for AWS environment), and i want to look at one of these.

          The pipeline view's javascript makes it very very hard to select which one of those parallel tasks I want to watch as it's scrolling down to the bottom every few seconds, so i basically have to wait until everything is done (half an hour) before i can even select the right build and see what happened IN THE BEGINNING of this build to figure out what's wrong.

          Next, if i manage to pick the correct parallel build it somehow still manages to switch the console output to the output of another build if that one's finished before the one i'm currently watching..

          To be honest, this autoscrolling behavior is useless for most of our scenarios as we run a lot of stuff in parallel.

          It might be ok to autoscroll-down if the user is already on the bottom of the page and you add more text, but don't mess with where my scrollbar is on the page otherwise. If i want to place it on the middle of the page to investigate something, let me do that. Currently the behaviour prohibits this as it's impossible to do anything but watch the last few lines as long as a build with a lot of text output is running.

          Either disable autoscrolling completely or only make it apply whenever a user has scrolled down to bottom.

          cetex oskar stenman added a comment - This is definitely not resolved, or handled by the referenced issue. Some builds we run ends up launching 15 parallel tasks (building AMI's for AWS environment), and i want to look at one of these. The pipeline view's javascript makes it very very hard to select which one of those parallel tasks I want to watch as it's scrolling down to the bottom every few seconds, so i basically have to wait until everything is done (half an hour) before i can even select the right build and see what happened IN THE BEGINNING of this build to figure out what's wrong. Next, if i manage to pick the correct parallel build it somehow still manages to switch the console output to the output of another build if that one's finished before the one i'm currently watching.. To be honest, this autoscrolling behavior is useless for most of our scenarios as we run a lot of stuff in parallel. It might be ok to autoscroll-down if the user is already on the bottom of the page and you add more text, but don't mess with where my scrollbar is on the page otherwise. If i want to place it on the middle of the page to investigate something, let me do that. Currently the behaviour prohibits this as it's impossible to do anything but watch the last few lines as long as a build with a lot of text output is running. Either disable autoscrolling completely or only make it apply whenever a user has scrolled down to bottom.
          kzantow Keith Zantow added a comment - - edited

          I'd also note: JENKINS-41088 is a slightly different ask, but could somewhat be accommodated by implementing this. I'll add that after using the tool for a while, I also find myself less interested in following along a particular stage than seeing the graph to click around. At one point, long ago, I did some work to "fix" this behavior somewhat, but it didn't disable following by default. Perhaps I can resurrect the pertinent parts of that if I get some time. Or perhaps a simple button to follow/not follow that's saved in browser storage or something similar would suffice; not sure the right UX for it – suggestions welcome.

          kzantow Keith Zantow added a comment - - edited I'd also note: JENKINS-41088 is a slightly different ask, but could somewhat be accommodated by implementing this. I'll add that after using the tool for a while, I also find myself less interested in following along a particular stage than seeing the graph to click around. At one point, long ago, I did some work to "fix" this behavior somewhat, but it didn't disable following by default. Perhaps I can resurrect the pertinent parts of that if I get some time. Or perhaps a simple button to follow/not follow that's saved in browser storage or something similar would suffice; not sure the right UX for it – suggestions welcome.
          timethos Tim Huang added a comment -

          Do we just have to kill this line?

          https://github.com/jenkinsci/blueocean-plugin/blob/b02273dc2a6aee295ac8bd7dbab8eb3a8516a60e/blueocean-dashboard/src/main/js/components/karaoke/components/LogConsole.jsx#L156

           

          This scroll bottom thing hurts more than it helps. It's easy enough for a user to hit fn + right arrow, or the end key...

          timethos Tim Huang added a comment - Do we just have to kill this line? https://github.com/jenkinsci/blueocean-plugin/blob/b02273dc2a6aee295ac8bd7dbab8eb3a8516a60e/blueocean-dashboard/src/main/js/components/karaoke/components/LogConsole.jsx#L156   This scroll bottom thing hurts more than it helps. It's easy enough for a user to hit fn + right arrow, or the end key...
          mspiller Matej Spiller added a comment -

          Any chance to get auto scrolling disabled? It is making blueocean very hard to use.

          Every time there is an output update from a build step the page is auto scrolled down. I understand this can be perhaps useful the first (once) time but not every time.

          When you have parallel builds. Click on one build that outputs a lot and then click Home on the keyboard or Page Up or any other key.

          After receiving new output page is scrolled to the bottom. And you can repeat this over and over again.

          The scrolling behaviour stops if I scroll the mouse wheel but any keypress (page up, page down, home, end, up, down) is keeping messing up the scrolling position.

          mspiller Matej Spiller added a comment - Any chance to get auto scrolling disabled? It is making blueocean very hard to use. Every time there is an output update from a build step the page is auto scrolled down. I understand this can be perhaps useful the first (once) time but not every time. When you have parallel builds. Click on one build that outputs a lot and then click Home on the keyboard or Page Up or any other key. After receiving new output page is scrolled to the bottom. And you can repeat this over and over again. The scrolling behaviour stops if I scroll the mouse wheel but any keypress (page up, page down, home, end, up, down) is keeping messing up the scrolling position.

          People

            Unassigned Unassigned
            gusgonnet72 Gustavo Gonnet
            Votes:
            6 Vote for this issue
            Watchers:
            18 Start watching this issue

            Dates

              Created:
              Updated: