Details
-
Task
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
-
1.0-m10, 1.0-m11
Description
As stages progress (ie the list of nodes finish, and there is no more log to see) focus should shift to the next flow node (stage).
In the case of a parallel branch, it can focus on the topmost branch until it is completed.
In scope:
- Step through of the experience of following a pipeline along with execution as shown by:https://docs.google.com/presentation/d/1jz_3mTH4rEldWlrHnm_04kHNtldItDhMXW2l3Ehqjio/edit#slide=id.g140c50d20d_0_0
Attachments
Issue Links
- blocks
-
JENKINS-35822 Developer can view an executing pipeline
-
- Resolved
-
Activity
tscherler looking great! so from what I can tell the confusing bit now is how to get back into the state of following along with the progress?
michaelneale yeah kind of, the problem is when you want to view e.g an earlier node you request something like http://localhost:8080/jenkins/blue/organizations/jenkins/steps/detail/steps/63/pipeline/5
the 5 on the end is the "node" id, now to be able to follow alone even on that url, is we test whether the url param node is smaller then nodeReducer and if so use the nodeReducer for the steps. Anyway if we not following but have a running job
Talking to michaelneale in the weekly I will try to change the onClick behaviour of the pipelineGraph in case of running nodes. In that case we do not point to a url like pipeline/${id} but remove the id
It is basically done, but since I merged latest master, which is busted, I need to fix that first
karaoke bug stoping will focus the selected node from the url (in our case node/5 https://youtu.be/8J3ETwkjjxg