-
Bug
-
Resolution: Fixed
-
Major
Users may configure Authorize Build plugin with the intention to limit who can run builds on the master in a setup where just going to zero static executors is impractical (e.g. to run a periodic backup or other housekeeping).
In that case, Pipelines cannot even start if started by users lacking Computer/Build on master, as the flyweight task cannot run there (and it seems to be tied to master).
(Reproduction using role-strategy only, as matrix-auth is currently lacking per-agent configuration)
CC jglick
- is related to
-
JENKINS-24513 Zero executors on master not well documented or enforced
- Closed
- relates to
-
JENKINS-31866 Attempts to restrict Pipeline jobs from running on master result in job hanging
- Open
-
JENKINS-55327 Job restrictions can be skipped if no node block in Jenkinsfile
- Closed
- links to