|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
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?