| Key: |
QB-126
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Robin Shen
|
| Reporter: |
Robin Shen
|
| Votes: |
3
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 29/Aug/06 06:51 PM
Updated: 23/Jan/07 04:27 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
From PMEase forum:
We use the hierarchy of configurations to define applications and promotion levels:
Code:
Application 1
test level 1
test level 2
release
Application 2
....
Only the promotion level configurations of the hierarchy have steps to be run. Is there a way to prevent users from being able to execute configurations that do not have any steps? I tried setting the 'build necessary condition' to false, but this does not prevent a manual build since the users can just change the condition to 'true'.
Maybe, someway to hide the gears icon on the dashboard if no steps are defined in the configuration?
|
|
Description
|
From PMEase forum:
We use the hierarchy of configurations to define applications and promotion levels:
Code:
Application 1
test level 1
test level 2
release
Application 2
....
Only the promotion level configurations of the hierarchy have steps to be run. Is there a way to prevent users from being able to execute configurations that do not have any steps? I tried setting the 'build necessary condition' to false, but this does not prevent a manual build since the users can just change the condition to 'true'.
Maybe, someway to hide the gears icon on the dashboard if no steps are defined in the configuration? |
Show » |
| There are no comments yet on this issue.
|
|
Be able to set certain configuration (especially non-leaf configurations) as non-buildable