Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49131

Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition

      1. If one (or more) parallel stage is skipped due to "when" condition in declarative pipeline, Blue Ocean UI does not show up running steps inside active stages until all steps in all active stages are finished.

      2. In such case If one of steps is "input" step, there is no option to "Proceed" or "Abort" using Blue Ocean UI since no steps are shown up. It can be done only using regular UI or console output.

      3. If all stages are active, steps are shown up, but after some time it is impossible to switch between output of "Stage A" to "Stage B" and see steps of "Stage B" until all steps in "Stage A" are finished. Refreshing page in browser (F5) allows switching between stages for some time.

      Example:

      // code placeholder
      pipeline {
       agent any
       parameters {
        choice(choices: 'NO\nEVEN\nODD', description: '', name: 'A')
        choice(choices: 'NO\nEVEN\nODD', description: '', name: 'B')
       }
       environment {
        A = "${params.A}"
        B = "${params.B}"
       }
       stages {
        stage('ParallelStages') {
         parallel {
          stage('Stage A') {
           when {
            anyOf {
             environment name: 'A', value: 'EVEN'
             environment name: 'A', value: 'ODD'
            }
           }
          steps {
           echo "Running Stage A"
           sleep 10
           echo "Finishing Stage A"
          }
         }
         stage('Stage B') {
          when {
           anyOf {
            environment name: 'B', value: 'EVEN'
            environment name: 'B', value: 'ODD'
           }
          }
          steps {
           echo "Running Stage B"
           sleep 30
           echo "Finishing Stage B"
           }
          }
         }
        }
       }
      }
      

       

       

          [JENKINS-49131] Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition

          Daniel Platz added a comment -

           Any update on this one? I am seeing the exact same issue on latest Jenkins builds (Jenkins (2.129)).

          Daniel Platz added a comment -  Any update on this one? I am seeing the exact same issue on latest Jenkins builds (Jenkins (2.129)).

          I am seeing the exact same issue too. 

          Pietro Ferrari added a comment - I am seeing the exact same issue too. 

          Jan Kacik added a comment - - edited

          We are too experiencing this on the latest LTS and plugins

          Jan Kacik added a comment - - edited We are too experiencing this on the latest LTS and plugins

          Chris Ladd added a comment -

          I'm seeing this with Jenkins 2.138.3 and Blue Ocean 1.14.0

          Chris Ladd added a comment - I'm seeing this with Jenkins 2.138.3 and Blue Ocean 1.14.0

          Elliot Graebert added a comment - - edited

          Hey folks, I'm seeing this, and it wasn't directly tied. The symptom is very similar: steps don't get populated until after the stage is done. It really ruins the Blue Ocean experience, as people just see blank stages. If those stages indicated a problem downstream that needs investigation, they have to check the artifact logs to figure it out.

           

          Jenkins 2.187 and Blue Ocean 1.18.0

          Elliot Graebert added a comment - - edited Hey folks, I'm seeing this, and it wasn't directly tied. The symptom is very similar: steps don't get populated until after the stage is done. It really ruins the Blue Ocean experience, as people just see blank stages. If those stages indicated a problem downstream that needs investigation, they have to check the artifact logs to figure it out.   Jenkins 2.187 and Blue Ocean 1.18.0

          Still reproducible with Jenkins 2.222.1 and Blue Ocean 1.22.0

          Artur Czarnota added a comment - Still reproducible with Jenkins 2.222.1 and Blue Ocean 1.22.0

          Juan added a comment -

          Still reproducible with Jenkins 2.289.1 and Blue Ocean 1.24.7

          Juan added a comment - Still reproducible with Jenkins 2.289.1 and Blue Ocean 1.24.7

          Drew Hagen added a comment -

          Still reproducible with Jenkins ver. 2.226 and Blue Ocean 1.22.0

          Drew Hagen added a comment - Still reproducible with Jenkins ver. 2.226 and Blue Ocean 1.22.0

          Marek Ohradka added a comment -

          Still an issue on Jenkins version 2.346.2 a Blue Ocean Version 1.25.8

          Marek Ohradka added a comment - Still an issue on Jenkins version 2.346.2 a Blue Ocean Version 1.25.8

            Unassigned Unassigned
            observer Michael Haskelsky
            Votes:
            21 Vote for this issue
            Watchers:
            26 Start watching this issue

              Created:
              Updated: