For example:
...
stage ('Stage 2') {
parallel (
'ATS path': {
node ("ghd13lite") {
println "On ATS path"
sleep 30
}},
'SPAM path' : {
node ("ghd13lite") {
println "On SPAM path"
stage ('Install SPAM') {
parallel (
'CE0': {
sleep 10
},
'CE1': {
sleep 20
}
)
}
stage ('Run SPAM') {
sleep 20
}
}
}
)
}
...
What I find is that the display doesn't match this structure during either
execution or after completion. What I expect to see is the SPAM path splitting
into two parallel paths and then converging back to the 'Run SPAM' activity.
Any advice on how to structure an imperative pipeline so that Blue Ocean has a
proper display would be welcome.
The 'real' version of this pipeline is rather involved with a lots of imports,
classes, logic, functions, etc. First attempts to convert to a declarative
pipeline did not go too smoothly :(.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CY1PR0301MB1996738AA011C6CA22273D88B8520%40CY1PR0301MB1996.namprd03.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.
