Details
-
Story
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Won't Fix
Description
Take a simple pipeline like:
stage "starting"
node {
stage "building"
sh "echo 42"
stage "testing"
sh "echo 43"
}
There is a bunch of work done by jenkins that is no reflected in the nodes returned for a stage:
Started by user mic@goo.com
[Pipeline] stage (starting)
Entering stage starting
Proceeding
[Pipeline] node
Running on master in /Users/michaelneale/projects/paas/blueocean/blueocean-plugin/work/workspace/pipey
[Pipeline] {
[Pipeline] stage (building)
Entering stage building
Proceeding
[Pipeline] sh
[pipey] Running shell script
+ echo 42
42
[Pipeline] stage (testing)
Entering stage testing
Proceeding
[Pipeline] sh
[pipey] Running shell script
+ echo 43
43
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
would it make sense to expose some of these "jenkins" nodes in the stage that they really come under (like starting the build, fetching a node, workspace etc).
Whilst showing all steps in a flowNode may be possible, showing these "synthetic" steps along with the users steps makes sense.
Attachments
Issue Links
- blocks
-
-
- Resolved
-
Activity
jdumay synthetic steps - I believe there is a backend ticket for exposing it but I am not sure where it is. We may want to differentiate how it is shown in the GUI as there can be a lot of them.
Note that one plugin actually uses the full flownode graph to display this:
code: https://github.com/jenkinsci/pipeline-view-plugin
I don't think it makes sense to show this in the stage graph, other than very simple flows, but it is useful information to show in the step listing.