-
Bug
-
Resolution: Unresolved
-
Minor
-
None
current promotion restriction require to set user names, and don't integrate with security settings. Should accept a group name.
current promotion restriction require to set user names, and don't integrate with security settings. Should accept a group name.
Setting a group name seems as hacky as setting a user name, just a bit more general.
Would it not be better to define a new permission (checked I guess on the parent job) for promoting a build, so that an authorization strategy can decide using normal idioms what users should be permitted?