Search

On pipelines with parallel stages, collapsing does not work correctly.
Stages seem to be collapsed, but some parts of the logs are randomly displayed outside collapsed sections though actually within the start and end stage regexp which are based on very specific strings displayed at stage start and end.

Our pipeline looks like :

Below is the first parallel section code :

stage('Build and Tests') {
parallel {
	stage('X86'){   // Build for X86 and run Simu tests
		stages{
			stage('SQuORE Analysis'){
				steps{ ... }
			}
			stage('Build X86'){
				steps{ ... }
			}
			stage('Unit Tests (with coverage)') {
				steps{ ... }
			}
			stage('Simu Tests'){
				steps{ ... }
			}
		}
	}
	stage('Doc Generation and Static Analysis'){
		stages{
			stage('Doc Generation') {
				steps{ ... }
			}
			stage('Local Doc Publication') {
				steps{ ... }
				}
			}
			stage('Static Analysis'){
				steps{ ... }
			}
		}                    
	}
	stage('Target Build & Packaging') {
		stages{
			stage('Target Build with Coverity') {
				steps{ ... }
			}
			stage('EVSE App Packaging'){
				steps{ ...}
			}
			stage('Coverity Analyze'){
				steps{ ... }
			}
		}
	} // End Stage 'Build and Tests on Target'   
} // End Parallel

For example, parts of the SQuORE Analysis or Unit Test stages are displayed though sections are collapsed.
And when opening a badly collpased section, it appears intricated within log lines from the other branches in the same parallel section, just as when collapse is not configured.

The collapse configuration is as follows :

Checking  One-per-line ending is even worst.

So... it appears that collapsing is unfortunately quite unusable with parallel stages, which is a mess as I hoped that it would offer a really better user experience with long console logs on complex pipelines.
Nevertheless, it correctly works with only sequential stages pipelines.