-
New Feature
-
Resolution: Unresolved
-
Major
We used the GitHub branch source plugin to automatically scan for repositories containing a Jenkinsfile. This works really well. However one of the missing features we run into is the fact that we can't specify permissions per new job (per repository) since we can only view the configuration and not save it.
We would like to keep using the project based authorization matrix and manually assign permissions for each newly detected GitHub repository.
michaelvantellingen
As you noticed, Jenkins doesn't currently support manually editing the configuration of calculated child items. Assuming that doesn't change, the settings for repos within an org would need to be configured at the org level or above - some kind of policy/template/formula or manual list as you mentioned.
Could you comment a bit more on what you might want this to look like?
Maybe a default child permission and then a matrix of of specific children to permissions?