| << Back to previous view |
|
[QB-123] More fine-grained permission control
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Robin Shen | Assigned To: | Robin Shen |
| Resolution: | Fixed | Votes: | 1 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Issue Links: |
|
||||||||
| Description |
|
Users that have permission to build should only be able to build a configuration with the default options. In other words I would like to prevent people from overriding settings when building
|
| Comments |
| Comment by Brian Surratt [ 03/Oct/06 08:51 AM ] |
| I'd like this because our numbering process is pretty eccentric. I can support it using some variables and such on the settings tab But if someone enters a value in the "Build as version" field, it might mess things. |
| Comment by Robin Shen [ 14/Dec/06 09:13 PM ] |
|
From Humberto Madeira, Another issue is that the security levels aren't fine grained enough. In order to trigger a promotion, a user has to have build access to the source build, as well as the destination build. Unfortunately this means they can also manually trigger the source build (which in this case is the nightly build - I don't want them to mess with it) Ideally I want to grant them "view" access to the source build and "build" access to the target build and that should be enough to allow them to promote the build. Alternatively, there could be a "promote" access level (between "view" and "build") |
| Comment by Robin Shen [ 14/Dec/06 09:15 PM ] |
|
From Humberto Madeira, I believe I mentioned before that it would be good to have an option to not show the trigger dialog, when triggering a build. Please add the ability to not show the promotion trigger dialog also. The problem is that there is nothing for the user to set, but they actually go ahead and set things anyways. |