[ https://issues.jenkins-ci.org/browse/JENKINS-10593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on JENKINS-10593 started by Joe Hansche. > Project-based Matrix Authorization Strategy: allow a job to not inherit from > global ACL > --------------------------------------------------------------------------------------- > > Key: JENKINS-10593 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10593 > Project: Jenkins > Issue Type: New Feature > Components: core > Affects Versions: current > Environment: Jenkins 1.424 > Reporter: oeuftete > Assignee: Joe Hansche > Priority: Minor > > It would be excellent if the Project-based Matrix Authorization Strategy > allowed for a project to start its authorizations from zero instead of > inheriting from the main configuration. > For example, while the vast majority of projects may only need the default > ACL, a restricted access project may need to be limited to only a few users > or groups. As I understand it, the Project-based Matrix Authorization > Strategy is additive. So to do this now. the global config would need to > have the barest set of authorizations, and every job (except the very > restricted one) would have to have the "Enable project-based security" > configuration specified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira