|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-16273) Slaves ... tangthe...@gmail.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... tangthe...@gmail.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... markusschult...@gmail.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... tg...@verizon.net (JIRA)
- [JIRA] (JENKINS-16273) Sl... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... tg...@verizon.net (JIRA)
- [JIRA] (JENKINS-16273) Sl... ra...@java.net (JIRA)
- [JIRA] (JENKINS-16273) Sl... bron...@real-time.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... bron...@real-time.com (JIRA)
- [JIRA] (JENKINS-16273) Sl... jesper.klit.jen...@intelligrated.com (JIRA)
We had this issue and were finally able to resolve it by granting the Anonymous user the "Connect" privilege under the "Slave" section. The permissions can be found in the "Authorization" section of the "Configure Global Security" page under "Manage Jenkins."