![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Oleg Nenashev
|
|
Components:
|
role-strategy, subversion |
|
Created:
|
21/Mar/14 8:27 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.
Steps to reproduce issue:
(TODO)
Actual Behavior:
(TODO)
Expected Behavior:
(TODO)
|
|
Environment:
|
- Jenkins, version 1.546 (latest LTS when this issue created).
- Jenkins Credentials Plugin (credentials), version 1.10 (latest when this issue created).
- Jenkins Subversion Plugin (subversion), version 2.2 (latest when this issue created).
- Jenkins Role Strategy Plugin (role-strategy), version 2.1.0 (latest when this issue created).
- JBoss Application Server 4.2.3.
|
|
Project:
|
Jenkins
|
|
Labels:
|
subversion
security
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Stephen Dharma
|
|
|
|
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.
