-
Bug
-
Resolution: Unresolved
-
Major
-
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
Sprint | New: Blue Ocean 1.2-beta4 [ 361 ] |
Rank | New: Ranked higher |
Description |
Original:
Take [this Pipeline run|https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/master/437/pipeline] 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. |
New:
Take [this Pipeline run|https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/master/437/pipeline] 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. [Video|https://www.dropbox.com/s/3sds6hof80mbzuo/JENKINS-45408.mov?dl=0] This is extremely annoying and makes getting additional information about failed Pipeline runs much more tedious than it should be. |
Description |
Original:
Take [this Pipeline run|https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/master/437/pipeline] 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. [Video|https://www.dropbox.com/s/3sds6hof80mbzuo/JENKINS-45408.mov?dl=0] This is extremely annoying and makes getting additional information about failed Pipeline runs much more tedious than it should be. |
New:
*Scope* Expanding any step should scroll to the bottom of the expanded step *Problem* [Video|https://www.dropbox.com/s/3sds6hof80mbzuo/JENKINS-45408.mov?dl=0] Take [this Pipeline run|https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/master/437/pipeline] 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. |
Epic Link | New: JENKINS-43952 [ 181484 ] |
Sprint | Original: Blue Ocean 1.2-beta4 [ 361 ] | New: Blue Ocean 1.3 [ 296 ] |
Rank | New: Ranked lower |
Sprint | Original: Blue Ocean 1.3-beta-2 [ 296 ] | New: Blue Ocean 1.4 [ 311 ] |
I get this same result. I'm using Chrome and Blue Ocean 1.1.2.