 |
History
| Log In
|
|
|
|
I agree with Timothy.
The reason I vote for this is that we plan to have a large network of machines building totally unrelated products. Unfortunately, without this feature, build system administrators will have to deal with all configurations (which might reach hundreds). Using proofbuild without finer-grained admin permissions is proving problematic for us. It would also work to have admin permissions restricted to, say, editing the repositories instead of steps (for different commit message).
The proof build issue can be addressed by parameterizing various properties (such as commit message) using variables and have variables prompt at build time. Refer to administration guide on your specific repository for more details.
I'd like this feature too. I've had to make everyone an administrator in the mean time, which isn't ideal.
This is a must have for us -we have way to many admins now which have access to administration areas they should not have.
There should be an 'Edit Configuration' access level which can be set by user/group and configuration. | ||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Closed
Major
Be able to assign subtree administrative rights to non-admin accounts
Not sure it it is easier to implement but their should a permission that we can set to a configuration item that give the modify permissions to the steps and other configurable items in that configuration.