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

[Baptiste Mathus]

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

Cheers

--
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-use...@googlegroups.com.
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.

[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: jenkins...@googlegroups.com <jenkins...@googlegroups.com> on behalf of Baptiste Mathus <m...@batmat.net>
Sent: 03 July 2018 14:24:00
To: 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 <aszo...@partner.eso.org<mailto:aszo...@partner.eso.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 jenkinsci-use...@googlegroups.com<mailto:jenkinsci-users%2Bunsu...@googlegroups.com>.

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 jenkinsci-use...@googlegroups.com<mailto:jenkinsci-use...@googlegroups.com>.
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>.

[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

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3694cc37234f454faa76fc2b2730a6c1%40partner.eso.org.

[Cuong Tran]

See https://github.com/jenkinsci/job-restrictions-plugin/pull/16