![]() |
|
|
|
|
Change By:
|
Stephen Dharma
(21/Mar/14 8:38 AM)
|
|
Description:
|
Currently when using Jenkins with "Subversion Plugin" and "Role Strategy Plugin", the Administrator does not have any control on how to manage "Subversion Credentials" privileges between different teams.
Prerequisite:
- Jenkins Credentials Plugin installed.
- Jenkins Subversion Plugin installed.
- Jenkins Role Strategy Plugin installed.
- Access Control - Security Realm: "Jenkins’ own user database".
- Access Control - Authorization: "Role-Based Strategy".
- Role "admin" (Global Privileges: all).
- Role "Team-A-Administrators" (Global Privileges: Overall-Read, Job-Create)(Project Privileges, Pattern TeamA.*: Job-all, Run-all).
- Jenkins Root Administrator User Account (e.g. "administrator") with Role "admin" (All Privileges).
- Team-A Administrator User Account (e.g. "adminteama") with Role "Team-A-Administrators".
Steps to reproduce issue:
(TODO)
Actual Behavior:
(TODO)
Expected Behavior:
(TODO)
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
