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?
Improvement
Resolved
Major
Be able to set certain configuration (especially non-leaf configurations) as non-buildable