Run one pipeline script on all nodes?

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Run one pipeline script on all nodes?

Sandra Parsick
Hello Mailinglist,

is it possible to run a pipeline script on all Jenkins nodes?

Thanks and best regards,

Sandra

--
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/39cefda5-feac-4d92-8b52-063958f7aaa5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Run one pipeline script on all nodes?

Mark Waite-2

On Sun, Apr 8, 2018 at 4:05 AM 'Sandra Parsick' via Jenkins Users <[hidden email]> wrote:
Hello Mailinglist,

is it possible to run a pipeline script on all Jenkins nodes?


It depends what you mean by "all Jenkins nodes".  Jenkins includes the concept of "permanent agents" which persist between jobs and ephemeral ("on-demand") agents that are created and destroyed as needed (most recently with Docker containers, though full virtual machines are used as well).

I assume you want to run your Pipeline script on all permanent agents.

The Elastic Axis plugin will allow a Freestyle job to run on all agents which match a label expression.  The platformlabeler plugin will automatically apply labels to agents using information about the agent (for example, the operating system installed on the agent).  I run Freestyle jobs on all the Linux and Windows agents in my build cluster with the Elastic Axis plugin and a label expression "linux || windows".

I think the same technique could be used in a Pipeline job, requesting the list of permanent agents, then creating a task for each of the agents in the list.  I haven't done that yet (still using Elastic Axis and platformlabeler), but I think it should be possible.

Mark Waite

 
Thanks and best regards,

Sandra

--
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/39cefda5-feac-4d92-8b52-063958f7aaa5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/CAO49JtGRCG5yVdHF8UH9_G2RY1%3DLC5iz9cQ8jqv2v-dN7WWd_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Run one pipeline script on all nodes?

Mark Waite-2


On Sunday, April 8, 2018 at 8:07:03 AM UTC-6, Mark Waite wrote:

On Sun, Apr 8, 2018 at 4:05 AM 'Sandra Parsick' wrote:
Hello Mailinglist,

is it possible to run a pipeline script on all Jenkins nodes?


It depends what you mean by "all Jenkins nodes".  Jenkins includes the concept of "permanent agents" which persist between jobs and ephemeral ("on-demand") agents that are created and destroyed as needed (most recently with Docker containers, though full virtual machines are used as well).

I assume you want to run your Pipeline script on all permanent agents.

The Elastic Axis plugin will allow a Freestyle job to run on all agents which match a label expression.  The platformlabeler plugin will automatically apply labels to agents using information about the agent (for example, the operating system installed on the agent).  I run Freestyle jobs on all the Linux and Windows agents in my build cluster with the Elastic Axis plugin and a label expression "linux || windows".


I just confirmed that the platformlabeler plugin is not currently available from the update center.  Sorry about that.

Daniel Beck believes that absence from the update center may be due to an infrastructure improvement he made.  If you decide to use the platformlabeler plugin and don't find it in the Update Center, an alternate download location is mentioned in Daniel's comments.

Mark Waite
 
I think the same technique could be used in a Pipeline job, requesting the list of permanent agents, then creating a task for each of the agents in the list.  I haven't done that yet (still using Elastic Axis and platformlabeler), but I think it should be possible.

Mark Waite

 
Thanks and best regards,

Sandra 

--
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/04b6846c-9c5d-4311-8c3e-e6fe99dcc3b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Run one pipeline script on all nodes?

Sandra Parsick
thank you

Am Sonntag, 8. April 2018 23:25:11 UTC+2 schrieb Mark Waite:


On Sunday, April 8, 2018 at 8:07:03 AM UTC-6, Mark Waite wrote:

On Sun, Apr 8, 2018 at 4:05 AM 'Sandra Parsick' wrote:
Hello Mailinglist,

is it possible to run a pipeline script on all Jenkins nodes?


It depends what you mean by "all Jenkins nodes".  Jenkins includes the concept of "permanent agents" which persist between jobs and ephemeral ("on-demand") agents that are created and destroyed as needed (most recently with Docker containers, though full virtual machines are used as well).

I assume you want to run your Pipeline script on all permanent agents.

The Elastic Axis plugin will allow a Freestyle job to run on all agents which match a label expression.  The platformlabeler plugin will automatically apply labels to agents using information about the agent (for example, the operating system installed on the agent).  I run Freestyle jobs on all the Linux and Windows agents in my build cluster with the Elastic Axis plugin and a label expression "linux || windows".


I just confirmed that the platformlabeler plugin is not currently available from the update center.  Sorry about that.

Daniel Beck believes that absence from the update center may be due to an infrastructure improvement he made.  If you decide to use the platformlabeler plugin and don't find it in the Update Center, an <a href="https://repo.jenkins-ci.org/javanet2-cache/org/jvnet/hudson/plugins/platformlabeler/1.1/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Fjavanet2-cache%2Forg%2Fjvnet%2Fhudson%2Fplugins%2Fplatformlabeler%2F1.1%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGSAuuRJdecPcQgUqI3b3F8QSfmOg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Frepo.jenkins-ci.org%2Fjavanet2-cache%2Forg%2Fjvnet%2Fhudson%2Fplugins%2Fplatformlabeler%2F1.1%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGSAuuRJdecPcQgUqI3b3F8QSfmOg&#39;;return true;">alternate download location is mentioned in <a href="https://groups.google.com/forum/#!topic/jenkinsci-users/h1XGhsnyiOc" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-users/h1XGhsnyiOc&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/forum/#!topic/jenkinsci-users/h1XGhsnyiOc&#39;;return true;">Daniel's comments.

Mark Waite
 
I think the same technique could be used in a Pipeline job, requesting the list of permanent agents, then creating a task for each of the agents in the list.  I haven't done that yet (still using Elastic Axis and platformlabeler), but I think it should be possible.

Mark Waite

 
Thanks and best regards,

Sandra 

--
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/25cc143e-c849-40d9-a742-f56488be3478%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Run one pipeline script on all nodes?

Ron Gebauer
In reply to this post by Mark Waite-2
Hello Mark,

I found another way.

In Jenkins pipelines you are able to set a parallel action where you can define on which nodes (I think both types) a task can run.

Best regards
Ron Gebauer

Am Sonntag, 8. April 2018 16:07:03 UTC+2 schrieb Mark Waite:

On Sun, Apr 8, 2018 at 4:05 AM 'Sandra Parsick' via Jenkins Users <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="1uPW4xYaBwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkins...@googlegroups.com> wrote:
Hello Mailinglist,

is it possible to run a pipeline script on all Jenkins nodes?


It depends what you mean by "all Jenkins nodes".  Jenkins includes the concept of "permanent agents" which persist between jobs and ephemeral ("on-demand") agents that are created and destroyed as needed (most recently with Docker containers, though full virtual machines are used as well).

I assume you want to run your Pipeline script on all permanent agents.

The Elastic Axis plugin will allow a Freestyle job to run on all agents which match a label expression.  The platformlabeler plugin will automatically apply labels to agents using information about the agent (for example, the operating system installed on the agent).  I run Freestyle jobs on all the Linux and Windows agents in my build cluster with the Elastic Axis plugin and a label expression "linux || windows".

I think the same technique could be used in a Pipeline job, requesting the list of permanent agents, then creating a task for each of the agents in the list.  I haven't done that yet (still using Elastic Axis and platformlabeler), but I think it should be possible.

Mark Waite

 
Thanks and best regards,

Sandra

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="1uPW4xYaBwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-users/39cefda5-feac-4d92-8b52-063958f7aaa5%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-users/39cefda5-feac-4d92-8b52-063958f7aaa5%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-users/39cefda5-feac-4d92-8b52-063958f7aaa5%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-users/39cefda5-feac-4d92-8b52-063958f7aaa5%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
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/e4bc0c0c-2f30-4cbf-9fd7-6835c2351e54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.