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 Jesse Glick
|Remote Link||This issue links to "CloudBees Internal OSS-2540 (Web Link)" [ 18256 ]|
|Assignee||Jesse Glick [ jglick ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Remote Link||This issue links to "core PR 3254 (Web Link)" [ 19919 ]|
|Remote Link||This issue links to "workflow-job PR 85 (Web Link)" [ 19920 ]|
|Remote Link||This issue links to "workflow-durable-task-step PR 61 (Web Link)" [ 19921 ]|
|Status||In Progress [ 3 ]||In Review [ 10005 ]|
|Status||In Review [ 10005 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|