|
||||||||
|
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/d/optout.
Well in practice it is not so obvious.
Also there are some use cases for administrators to configure special projects that must run on the master, to do backups and the like. For these cases you want to leave some executor slots open, yet block regular projects from using them. The natural way to do that would be to have Jenkins.MasterComputer.checkPermission(Computer.BUILD) require RUN_SCRIPTS on Jenkins, so that only admin-authorized projects could run on it; and then display an admin monitor when security is enabled yet there is no configured QueueItemAuthenticator.