Pipeline jobs always require master

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

Pipeline jobs always require master

Artur Szostak
Dear all,

I am using the Job Restrictions plugin to enforce that no jobs run on the Jenkins master except administrative jobs. While trying to then setup a number of pipeline jobs, it appears that no matter how I encode the pipeline DSL, it will always require the master build node to start executing. Is this really the case that pipeline jobs must have access at least to the executer queue on master?

Kind regards.

Artur

--
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/0e118c36aeba4bcebe2ebe7b4f96a1ef%40partner.eso.org.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Pipeline jobs always require master

Baptiste MATHUS
Definitely nope. You can set executors to 0 on master (as it should) and your pipelines will still run.

Cheers

Le ven. 29 juin 2018 à 16:36, Artur Szostak <[hidden email]> a écrit :
Dear all,

I am using the Job Restrictions plugin to enforce that no jobs run on the Jenkins master except administrative jobs. While trying to then setup a number of pipeline jobs, it appears that no matter how I encode the pipeline DSL, it will always require the master build node to start executing. Is this really the case that pipeline jobs must have access at least to the executer queue on master?

Kind regards.

Artur

--
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/0e118c36aeba4bcebe2ebe7b4f96a1ef%40partner.eso.org.
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/CANWgJS6Vb7kWsPLj3Q%2BEZ5zX2EczcZYzByum62tFfitMdGN_UQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Pipeline jobs always require master

Artur Szostak
And yet, using the Job Restrictions plugin clearly shows that some kind of kickstart / bootstrap (whatever you want to call it) sub task attempts to run on master and will block the whole pipeline job if a special exception is not made to the permissions for pipeline jobs.

I later found the following ticket that seems to relate to the symptoms that I experience: https://issues.jenkins-ci.org/browse/JENKINS-31866

Cheers

Artur
________________________________________
From: [hidden email] <[hidden email]> on behalf of Baptiste Mathus <[hidden email]>
Sent: 03 July 2018 14:24:00
To: [hidden email]
Subject: Re: Pipeline jobs always require master

Definitely nope. You can set executors to 0 on master (as it should) and your pipelines will still run.

Cheers

Le ven. 29 juin 2018 à 16:36, Artur Szostak <[hidden email]<mailto:[hidden email]>> a écrit :
Dear all,

I am using the Job Restrictions plugin to enforce that no jobs run on the Jenkins master except administrative jobs. While trying to then setup a number of pipeline jobs, it appears that no matter how I encode the pipeline DSL, it will always require the master build node to start executing. Is this really the case that pipeline jobs must have access at least to the executer queue on master?

Kind regards.

Artur

--
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]<mailto:jenkinsci-users%[hidden email]>.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0e118c36aeba4bcebe2ebe7b4f96a1ef%40partner.eso.org.
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]<mailto:[hidden email]>.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6Vb7kWsPLj3Q%2BEZ5zX2EczcZYzByum62tFfitMdGN_UQ%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6Vb7kWsPLj3Q%2BEZ5zX2EczcZYzByum62tFfitMdGN_UQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
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/3694cc37234f454faa76fc2b2730a6c1%40partner.eso.org.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Pipeline jobs always require master

Baptiste MATHUS
Definitely looks like a bug *in the Job Restrictions plugin*. This should work in general, so you likely want to focus on fixing that plugin indeed.

Cheers

Le mer. 4 juil. 2018 à 20:18, Artur Szostak <[hidden email]> a écrit :
And yet, using the Job Restrictions plugin clearly shows that some kind of kickstart / bootstrap (whatever you want to call it) sub task attempts to run on master and will block the whole pipeline job if a special exception is not made to the permissions for pipeline jobs.

I later found the following ticket that seems to relate to the symptoms that I experience: https://issues.jenkins-ci.org/browse/JENKINS-31866

Cheers

Artur
________________________________________
From: [hidden email] <[hidden email]> on behalf of Baptiste Mathus <[hidden email]>
Sent: 03 July 2018 14:24:00
To: [hidden email]
Subject: Re: Pipeline jobs always require master

Definitely nope. You can set executors to 0 on master (as it should) and your pipelines will still run.

Cheers

Le ven. 29 juin 2018 à 16:36, Artur Szostak <[hidden email]<mailto:[hidden email]>> a écrit :
Dear all,

I am using the Job Restrictions plugin to enforce that no jobs run on the Jenkins master except administrative jobs. While trying to then setup a number of pipeline jobs, it appears that no matter how I encode the pipeline DSL, it will always require the master build node to start executing. Is this really the case that pipeline jobs must have access at least to the executer queue on master?

Kind regards.

Artur

--
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]<mailto:[hidden email]>.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0e118c36aeba4bcebe2ebe7b4f96a1ef%40partner.eso.org.
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]<mailto:[hidden email]>.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6Vb7kWsPLj3Q%2BEZ5zX2EczcZYzByum62tFfitMdGN_UQ%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6Vb7kWsPLj3Q%2BEZ5zX2EczcZYzByum62tFfitMdGN_UQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
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/3694cc37234f454faa76fc2b2730a6c1%40partner.eso.org.
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/CANWgJS4Aqk0M_CXggejFcKVmmfNYJxFOEZsPsihWFeTPOdPmjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Pipeline jobs always require master

Cuong Tran
In reply to this post by Artur Szostak
See https://github.com/jenkinsci/job-restrictions-plugin/pull/16

On Wednesday, July 4, 2018 at 1:18:55 PM UTC-5, Artur Szostak wrote:
And yet, using the Job Restrictions plugin clearly shows that some kind of kickstart / bootstrap (whatever you want to call it) sub task attempts to run on master and will block the whole pipeline job if a special exception is not made to the permissions for pipeline jobs.

I later found the following ticket that seems to relate to the symptoms that I experience: <a href="https://issues.jenkins-ci.org/browse/JENKINS-31866" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-31866\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFYDZYCUSgB-UEvoKxfaZM_SaTgjA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-31866\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFYDZYCUSgB-UEvoKxfaZM_SaTgjA&#39;;return true;">https://issues.jenkins-ci.org/browse/JENKINS-31866

Cheers

Artur
________________________________________
From: <a href="javascript:" target="_blank" gdf-obfuscated-mailto="NI-PvRxsBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkins...@googlegroups.com <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="NI-PvRxsBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkins...@googlegroups.com> on behalf of Baptiste Mathus <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="NI-PvRxsBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">m...@...>
Sent: 03 July 2018 14:24:00
To: <a href="javascript:" target="_blank" gdf-obfuscated-mailto="NI-PvRxsBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkins...@googlegroups.com
Subject: Re: Pipeline jobs always require master

Definitely nope. You can set executors to 0 on master (as it should) and your pipelines will still run.

Cheers

Le ven. 29 juin 2018 à 16:36, Artur Szostak <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="NI-PvRxsBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">aszo...@...<mailto:<a href="javascript:" target="_blank" gdf-obfuscated-mailto="NI-PvRxsBQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">aszo...@....org>> a écrit :
Dear all,

I am using the Job Restrictions plugin to enforce that no jobs run on the Jenkins master except administrative jobs. While trying to then setup a number of pipeline jobs, it appears that no matter how I encode the pipeline DSL, it will always require the master build node to start executing. Is this really the case that pipeline jobs must have access at least to the executer queue on master?

Kind regards.

Artur

--
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/c0e7fd46-f5d5-4d88-8969-8da3ea159dab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.