Thanks, I have just signed up, watched and voted. ;)

Anyway, I am still learning the pipeline so please pardon me if I make any 
mistake in my script. I have also attached a screenshot of how it looks at 
this moment in BlueOcean.

stage("Build and test") {
    parallel 'Slave1':{
        node('TestSlave1') {
            stage ('configure') {
             ...
            }
            stage ('make') {
             ...
            }
            stage ('test') {
             ...
            }
        }
       
    }, 'Slave2':{
        node('TestSlave2') {
            stage ('configure') {
             ...
            }
            stage ('make') {
             ...
            }
            stage ('test') {
             ...
            }
        }
    }, 'Slave3':{
        node('TestSlave3') {
            stage ('configure') {
             ...
            }
            stage ('make') {
             ...
            }
            stage ('test') {
             ...
            }
        }
    }
}
stage('Deploy') {
    ...
}





On Friday, December 16, 2016 at 10:40:32 AM UTC+13, James Dumay wrote:
>
> Alan how would you write the Jenkinsfile for that example?
>
> On Fri, Dec 16, 2016 at 8:39 AM James Dumay <[email protected] 
> <javascript:>> wrote:
>
>> Thats great info Alan. BTW you should watch and vote for this ticket 
>> https://issues.jenkins-ci.org/browse/JENKINS-38442 
>>
>> On Fri, Dec 16, 2016 at 8:35 AM Alan Wu <[email protected] 
>> <javascript:>> wrote:
>>
>>> Thanks so much for all the quick responses.
>>>
>>> Personally I think having the ability to visualise nested stages within 
>>> each parallel node are important. 
>>>
>>> Says if I now have the parallel block within a stage called "Build and 
>>> test" and add in a "deploy" stage after it,
>>> here is my two cents on how I imagine my use case should look. 
>>>
>>>                          / Slave1 -- configure -- build -- test \
>>>   Build and test - Slave2 -- configure -- build -- test - deploy
>>>                          \ Slave3 -- configure -- build -- test /
>>>
>>>
>>>
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-dev/msDK4In10QU/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> [email protected] <javascript:>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/16e500b9-e0bf-4f58-9c5b-9a766dfd6a17%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/16e500b9-e0bf-4f58-9c5b-9a766dfd6a17%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> -- 
>> James Dumay
>> Product Manager
>> CloudBees, Inc.
>> Skype: jdumaycb Twitter: i386
>>
> -- 
> James Dumay
> Product Manager
> CloudBees, Inc.
> Skype: jdumaycb Twitter: i386
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c6e3414d-e566-4569-abd9-476e97861442%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to