I would just like to point out a note from pipeline paper I am reading. It
is as follows,
Stages are usually the top most element of Pipeline syntax. Stages allow
you to group your build step into its component parts. By default, multiple
builds of the same pipeline can run concurrently. The stage element also
allows you to control this concurrency:
The above seem to suggest that stage is necessary to control concurrency.
Also, one more follow-up question. If I were to build on multiple nodes
then how would results from one node be available to the other node.
I assume node can be an independent machine with its own workspace.
On Thursday, 26 January 2017 20:34:58 UTC+5:30, jer...@bodycad.com wrote:
> I may not have all answer here, but here a start.
>
> stage serve no purpose except giving visual queue and split console data
> into the view as far as I know. It also split the time used to complete.
>
> For the node, they are sequential unless you use the parallel instruction.
> So you probably need to build on a possible node first then parallel the
> unit test execution:
>
> node('buildrequirement')
> {
> // build instruction here
> }
> parallel
> (
> platform1:
> {
> node('platform1requirements')
> {
> // run unit test on platform 1
> }
> },
> platform2:
> {
> node('platform2requirements')
> {
> // run unit test on platform 2
> }
> }
> )
>
> For better parallel example:
>
> https://github.com/jenkinsci/pipeline-examples/blob/master/pipeline-examples/jobs-in-parallel/jobs_in_parallel.groovy
>
--
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/c1e5536f-0753-4e81-8c76-5b64d3fd25ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
