Paolo Brocco hey thanks for the detailed report (I wish they were all as good!). I suspect this is a duplicate of JENKINS-35836 - does that sound right to you? If you could verify that would help here.

James Dumay oh sorry I didn't see the duplicate, maybe because it was closed...

as you wrote in the other issue "it is unlikely that we will be able to satisfy everyone with any of the suggested resolutions" I guess that the destiny of this one will be the same... closed as "Won't do".

I guess we'll live with that: always switching back and forth between blue ocean and the "classic view" because blue ocean doesn't show all the logs as one would expect...

Paolo Brocco the easiest way to make the visualization work the way you want it is to ensure everything sits within a stage block.

So for example, if you had:

stage('cool stage') {
  echo 'Starting coolness'
  parallel (...)
  echo 'Ended coolness'
}

Then you could instead write:

stage('preparing cool') {
    echo 'Starting coolness'
}
stage('cool stage') {
  parallel (...)
}
stage('finishing cool') {
    echo 'Ended coolness'
}

You would then be able to access all steps from the UI.

There are a number of styles of Pipelines that we can't support (at least for the moment) due to Pipeline scripts rather open ended design. Of course, Declarative Pipeline will not allow you to write Pipelines that cannot be visualised.

Sorry we can't be much help here.

Paolo Brocco unfortunately scripted pipeline is a full programming language, it isn't possible to show that visually for all cases. In this case it would be nice to have a fallback that "flattens things out" etc... and perhaps could one day, but with the growing popularity of declarative, it is an easier option to stay within the realms of something visualisable.