-
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
[JENKINS-46652] Authorize Project blocks Pipeline Jobs when Computer/Build for master is lacking
Link |
New:
This issue is related to |
Labels | New: permissions |
Remote Link | New: This issue links to "CloudBees Internal OSS-2540 (Web Link)" [ 18256 ] |
Assignee | New: Jesse Glick [ jglick ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "core PR 3254 (Web Link)" [ 19919 ] |
Remote Link | New: This issue links to "workflow-job PR 85 (Web Link)" [ 19920 ] |
Remote Link | New: This issue links to "workflow-durable-task-step PR 61 (Web Link)" [ 19921 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |