-
Bug
-
Resolution: Won't Do
-
Minor
-
None
-
Jenkins: 2.1
git-client-plugin: 1.19.6
Pipeline: SCM Step: 2.1
We don't want to run any user defined code on our master in order to make behavioral guarantees about the node. See the google groups discussion for more information: https://groups.google.com/forum/#!topic/jenkinsci-users/FRfL4RHAYnk
We'd like to be able to set a specific label that can be used for running the flyweight executors
[JENKINS-35710] Option to not run pipeline flyweight executors on master
Mathieu Clabaut
added a comment - Another use case is when nodes are used to separate repository in order to limit access right.
For example, everything concerning project P is done in node node-P with a specific user having access by ssh keys to project P on main repo…
Not being able to run pipeline scripts in a node, force to break the scheme and give the jenkins user right on all the repo, which is not intended.
Mathieu Clabaut
added a comment - Another use case is when nodes are used to separate repository in order to limit access right.
For example, everything concerning project P is done in node node-P with a specific user having access by ssh keys to project P on main repo…
Not being able to run pipeline scripts in a node, force to break the scheme and give the jenkins user right on all the repo, which is not intended. matclab I think you are looking for a way to limit which users may configure jobs to run on selected nodes. AFAIK there is no such OSS Jenkins feature; there is one in CloudBees Jenkins Platform. Anyway not specific to Pipeline.
The flyweight executors are just a fiction for visualization. Pipeline script runs inside the master JVM. There is no way to run it elsewhere without a major reimplementation.