Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
-
-
1.0-beta-1
Description
Problem
Opening a pipeline that is RUNNING but has no steps shows the final stage incorrectly selected
- I believe this occurs when there are not any flow nodes available but the Pipeline is running.
- The last stage is selected and it says there are no steps.
- When we get flow nodes it switches to the executing stage.
What should happen
- The user should see the screen below.
- The first step is always selected and the empty state says that it is "waiting for the run to start".
- This is based on the simple rule of "no steps + running".
jamesdumay how important is that you see the steps? The steps are based on the last successful run of a pipeline. In theory we do not know the steps until we are processing them.
Current solution is simply not showing the steps when the job is queued. I would need to look into "tricking" the pipelineGraph to show the first node selected, but IMO the suggested implementation is cleaner. ....but your call