Using Blue Ocean with an Imperative Pipeline

25 views
Skip to first unread message

Gardell, Steven

unread,
Feb 24, 2017, 10:21:56 AM2/24/17
to jenkins...@googlegroups.com

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 L.

Reply all
Reply to author
Forward
0 new messages