jamesdumay This is pretty bad. I think as an immediate action we could at least print a warning when some steps are not displayed – because that will confuse lots of users:

«Warning! This pipeline contains steps that can not be displayed in Blue Ocean. Please go to [classic UI] to see all the steps. Read more in JENKINS-35836.»

JENKINS-35836 is a link to this,
[classic UI] is a link to the build "pipeline steps" view.

roidelapluie we were discussing warnings today. Stay tuned!

Hi all,

I want to be honest that it is unlikely that we will be able to satisfy everyone with any of the suggested resolutions on this ticket and that I will be closing this out.

However, if any community member has a bright idea on how to solve it and wants to try to make it work we'd be more than happy to guide and assist.

As per the description, there are two workarounds given that help solve this problem - and one is the brand new Declarative Pipeline syntax which was designed to solve this exact problem.

Thanks,
James

I'm not sure how the Declarative Pipeline Syntax solves this problem - when I try to define:

pipeline {
  agent none
  stages {
    stage('My stage') {
      steps {
        echo 'outside'
        parallel {
            stage('A') {
                echo 'a'
            }
            stage('B') {
                echo 'a'
            }
        }
      }
    }
  }
}

I get a syntax error:

Invalid step "parallel" used - not allowed in this context - The parallel step can only be used as the only top-level step in a stages step block

My workaround is possibly to use xargs -P or GNU parallel, but it would be a pain if the branches are Groovy code.

Also, if you have an error like a test failure in the outside are that is not inside parallel, opening the build actually sends you to /blue/organizations/jenkins/:pipeline/detail/:pipeline/:build_number/pipeline which shows everything. So it doesn't seem true that the output is not visualized, just that it is not reachable through navigation. Try this to reproduce:

node {
    stage 'My stage', {
        def actions = [:]
        actions['a'] = {
            echo 'a'
        }
        actions['b'] = {
            echo 'b'
        }
        parallel actions
        sh 'echo feels good to be outside parallel'
        throw new RuntimeException("outside, later error")
    }
}

It gives this perfectly good output:

However, it only renders this if there is a failure outside parallel.

As for ideas:

• make this output available even if there is no failure in that area rather than selecting the last parallel stage by default.
• make the stage name (on the Start...End line) clickable, to open this full output.