Quess I am confused about “node” in pipeline

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Quess I am confused about “node” in pipeline

itchymuzzle

I thought “node” was a scripted pipeline thing, but item #4 in this:  [https://www.cloudbees.com/blog/top-10-best-practices-jenkins-pipeline-plugin] seems to disagree with that. 

 

So I am suppose to use “node” to ensure the Jenkins master doesn’t do any work?  Doesn’t setting executors to zero also ensure that?


Thanks

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/46409888-1c0a-445c-8a87-e231cc2b6b10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Quess I am confused about “node” in pipeline

itchymuzzle
I am using "label" to define what gets run where.  

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/52c48a85-5784-4739-bce5-3fd788e31edf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Quess I am confused about “node” in pipeline

Robert Hales
In reply to this post by itchymuzzle
Node is a build step. Any build steps can be run in a declarative pipeline, but you can also specify which node to use with 'agent' on a declarative pipeline. Everything runs initially on a flyweight executor on the master. Then it farms out the heavy lifting to the appropriate nodes you specify. If you don't specify a node or agent properly, you end up running everything on the flyweight executor. Setting executors to 0 on the master doesn't change that. It just prevents you from using 'agent' or 'node' to put the heavy lifting on the master. 

On Monday, November 6, 2017 at 8:41:41 AM UTC-7, itchymuzzle wrote:

I thought “node” was a scripted pipeline thing, but item #4 in this:  [<a href="https://www.cloudbees.com/blog/top-10-best-practices-jenkins-pipeline-plugin" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.cloudbees.com%2Fblog%2Ftop-10-best-practices-jenkins-pipeline-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEYIOHD0dZkpouhUGaQHlQtKVtIKw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.cloudbees.com%2Fblog%2Ftop-10-best-practices-jenkins-pipeline-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEYIOHD0dZkpouhUGaQHlQtKVtIKw&#39;;return true;">https://www.cloudbees.com/blog/top-10-best-practices-jenkins-pipeline-plugin] seems to disagree with that. 

 

So I am suppose to use “node” to ensure the Jenkins master doesn’t do any work?  Doesn’t setting executors to zero also ensure that?


Thanks

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/01222e34-f6ac-4848-9cef-4ac9527aced5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.