-
Bug
-
Resolution: Fixed
-
Major
-
-
pacific, atlantic, indian, arctic, tasman, iapetus, 1.0, Blue Ocean 1.0-rc3, Blue Ocean 1.0-rc4, Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2
Some times if the step listing takes a while to show, the pipeline results screen can show "There are no steps" empty state incorrectly, before being replaced with the step listing...
This requires some more investigation as at the moment when it shows no steps when a pipeline is completed this is a problem. When it is running (karaoke) the current behavior is fine. This is just for when a user is clicking around a completed pipeline.
- blocks
-
JENKINS-42318 UI Not Refreshing When Starting a Build
-
- Closed
-
-
JENKINS-40860 Go to the end of the expanded log
-
- Closed
-
-
JENKINS-36133 Animate in steps when stage node is clicked
-
- Resolved
-
- is duplicated by
-
JENKINS-44182 really hard to exit BO build page when build is ongoing and creates lots of console output.
-
- Closed
-
- relates to
-
JENKINS-39770 Pipeline visualization not rendered when there is more that 100 nodes
-
- Reopened
-
-
JENKINS-41885 Build log is scrolled down unconditionally on update
-
- Closed
-
-
JENKINS-41897 Karaoke: steps and nodes are limited to 100 - need to increase limit
-
- Closed
-
I am trying to get my head around how to prevent the flicker.
The basic problem is to determine when the component is still "waiting" for the step fetch to finish and return the result of the fetch. Or whether that fetch has finished and there are no steps related with the stage.
One observation in "block" pipeline is that empty nodes are not clickable anymore. I could use the same logic though. Will test whether that behaviour is as well the same in the classic pipeline syntax