Re: Pipeline - stage, node

[jerome]

I'm not sure they actually do this much, but you could totally put a stage 
around your parallel. If we take a look at the diagram on
https://jenkins.io/doc/book/pipeline/

stage{
  parallel(['toto': node(){ ... }])  
}

seem like a valid way.

I for one have a node that contain multiple stage and it doesn't disturb it.

node
{
  stage('build')
  {
...
  }
  stage('unit testing')
  {
...
  }
}


I think you cannot declare a stage inside a parallel, it would mess up the 
stages. It's my understanding of them so far, they kind of just indicate a 
split between flow group.  Maybe the dev people from Jenkins or more 
advanced users can shed more light on this.

-- 
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/f70f37a2-7a75-45d5-866a-cd20c5cf382f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline - stage, node

[Sharan Basappa]

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.

Re: Pipeline - stage, node

[jerome]

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/1fe75160-da21-4e17-b2ec-50b33bc875c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline - stage, node

[Daniel Beck]

> On 21.01.2017, at 19:24, Sharan Basappa  wrote:
> 
> I am stuck with conceptual understanding of pipeline.

Have you read https://jenkins.io/doc/book/pipeline/ ? Most of what you're 
asking is being answered there.

-- 
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/D4DFF062-6341-484F-A655-35062597CDE7%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline - stage, node

[Sharan Basappa]

can anyone be kind enough to respond to the query below of mine?
It would help me a lot

On Saturday, 21 January 2017 23:54:15 UTC+5:30, Sharan Basappa wrote:

> Hello,
>
> I am trying to adapt pipeline as a part of my project. I am starting with 
> a simple example, though, to get my understanding correct.
> However, after reading several white papers and even after being able to 
> write simple examples, I am stuck with conceptual understanding of pipeline.
>
> My first question is, what exactly is the use of stage. Looking at example 
> it is clear that it is used to segregate distinct build phases but the 
> question
> is, whether it is inserted just to get stage based view in the build 
> dashboard or there is more to it than this.
> I have also seen stage being used to segregate like build, test and 
> publish.
> Does it mean that these are executed in sequential?
>
> My second question is related to node. If I have 2 nodes, do they execute 
> in parallel invariably?
> Also, do different nodes create their own workspace?
>
> Continuing with nodes, assume I have to do compile, run tests. Also, I can 
> run two test suites in parallel (suite_1 and suite_2).
> Now, I need to build first and only then I can run the 2 test suites.
> How can I create nodes in this case?
> Also, if each node creates its own workspace then how can node that run 
> suite_1 and suite_2 access the compiled libraries
> that is created by first node that compiles?
>
> Thanks in advance ...
>
>

-- 
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/b7211a2e-97f2-4912-bdf0-11b046ce91b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline - stage, node

[Sharan Basappa]

Hello,

I am trying to adapt pipeline as a part of my project. I am starting with a 
simple example, though, to get my understanding correct.
However, after reading several white papers and even after being able to 
write simple examples, I am stuck with conceptual understanding of pipeline.

My first question is, what exactly is the use of stage. Looking at example 
it is clear that it is used to segregate distinct build phases but the 
question
is, whether it is inserted just to get stage based view in the build 
dashboard or there is more to it than this.
I have also seen stage being used to segregate like build, test and publish.
Does it mean that these are executed in sequential?

My second question is related to node. If I have 2 nodes, do they execute 
in parallel invariably?
Also, do different nodes create their own workspace?

Continuing with nodes, assume I have to do compile, run tests. Also, I can 
run two test suites in parallel (suite_1 and suite_2).
Now, I need to build first and only then I can run the 2 test suites.
How can I create nodes in this case?
Also, if each node creates its own workspace then how can node that run 
suite_1 and suite_2 access the compiled libraries
that is created by first node that compiles?

Thanks in advance ...

-- 
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/cf0f5ddd-31b5-4284-b35d-6e540e3f4eff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.