Details
-
Story
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Done
Description
To make workflow more compelling, Jenkins 2.0 should provide a better visualization of the workflow execution out of the box.
CloudBees is proposing to contribute the workflow stage view plugin to jump start this, which uses stage steps to drive the visualization of workflow runs as they progress through the pipeline:
Attachments
Issue Links
- is duplicated by
-
JENKINS-32675 Pipeline Plugin: Adjusting the Visualization of Pipeline Steps
-
- Resolved
-
- is related to
-
JENKINS-31118 Workflow jobs that are waiting for input should have a visual cue in build history
-
- Resolved
-
Activity
The workflow graph is still overly verbose: Allocate node : Start is always followed by Allocate node : Body : Start, likewise with the step output for dir, timestamps, timeout, ws, withEnv, withRegistry, retry, wrap.
This leads to unnecessarily deep trees and makes it difficult to parse. Can we collapse those nodes in the workflow graph to 1 deep instead of 2?
John Zila
added a comment - - edited The workflow graph is still overly verbose: Allocate node : Start is always followed by Allocate node : Body : Start , likewise with the step output for dir , timestamps , timeout , ws , withEnv , withRegistry , retry , wrap .
This leads to unnecessarily deep trees and makes it difficult to parse. Can we collapse those nodes in the workflow graph to 1 deep instead of 2? 4c00h unfortunately I'm afraid the Retry feature is exclusive to Cloudbees' Jenkins Enterprise. I'm also currently using Build Pipeline Plugin and I really miss the Retry feature. I hope Cloudbees decides to make this feature free/open source.
While we're already off-topic, in a closed ticket…
jzila: You'd have to open a new ticket for that.
dserodio: Or hope that Naginator (which works pretty good for retrying Freestyle builds) gets Pipeline support: JENKINS-37076
The workflow graph is still overly verbose
Changes in this area planned anyway.
the Retry feature is exclusive to Cloudbees' Jenkins Enterprise
The feature name you are probably referring to is checkpoints. Core (OSS) Pipeline supports a Retry feature, which is quite different.
I've noticed that the 'Retry' and 'Download' links don't appear by default. After looking at the code, there seems to be an extension mechanism for controlling this area of the UI.
We're currently using BuildPipeline steps and use the Restart functionality heavily. Is there any plans to make the Restart logic available with the StageView?