Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: blueocean-plugin
-
Labels:
-
Similar Issues:
Description
Similar to JENKINS-46809, I would like the Blue Ocean GUI to properly visualize multiple stages in sequence that are all parallel of each other. Below is an example image of what this looks like using declarative syntax (working):
Here is the declarative example code I wrote to generate the example image:
pipeline { agent { label 'master' } stages { stage('Build and Test') { parallel { stage("Build and Test Linux") { stages { stage("Build (Linux)") { agent any steps { echo "Inside for loop 1" } } stage("Test (Linux)") { agent any steps { echo "Inside for loop 2" } } } } stage("Build and Test Windows") { stages { stage("Build (Windows)") { agent any steps { echo "Inside for loop 3" } } stage("Test (Windows)") { agent any steps { echo "Inside for loop 4" } } } } } } } }
Here is example scripted Jenkins code that I would like to use. Linux and windows build/test flows happen in parallel. Inside each flow in a "build" stage and then a "test" stage. The Windows sequential build/test flow should be displayed in parallel with the Linux build/test flow, but right now the separate Build/Test sequential stages are combined into one circle/stage when using the scripted syntax.
pipeline { agent any stages { stage("Build and Test") { steps { script { parallel linux: { node("linux_build") { echo "Inside for loop 1" } node("linux_test") { echo "Inside for loop 2" } }, windows: { node("windows_build") { echo "Inside for loop 3" } node("windows_test") { echo "Inside for loop 4" } } } } } } }
This is what the scripted example code currently generates:
Attachments
Issue Links
- is related to
-
JENKINS-53751 The same parallel scripted and declarative pipelines rendered differently
-
- Resolved
-
- relates to
-
JENKINS-53048 Parallel sequential stages not rendering correctly
-
- Closed
-
-
JENKINS-53162 Blueocean support for visualizing stages in parallel block in scripted pipeline
-
- Closed
-
Contra Olivier Lamy’s comment there I consider this a bug. Blue Ocean should pay attention to the build metadata as provided by official Pipeline APIs and may not make assumptions about the mechanism used to run a build, except insofar as that is intrinsically required for a certain feature. (For example, a stage restart button should only appear next to a Declarative stage, because the feature of restarting a stage is tied to Declarative semantics.)
Regardless of how the issue is classified, the question of whether it will be fixed or not depends entirely on the development team’s time and priorities.