|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Magnus,
There are two different accesses to think about - the PrioritySorter global settings (JobGroups), and then the setting for an individual job.
If Jenkins is secured (there are quite a lot of different ways this can be done), then clearly anonymous should not be allowed to change any PrioritySorter settings.
Is your idea that any logged in (authenticated) user can change any PrioritySorter settings?
I would prefer that only an admin user can change the global PrioritySorter settings. Any user who has job-level configure rights can set the priority in an individual job (I think that comes automatically and you donlt need to code anything).
Job-level configure rights apply with https://wiki.jenkins-ci.org/display/JENKINS/Matrix-based+security or any of the schemes that inherit from it.
I hope that makes sense.
Thanks
Matthew