|
||||||||
|
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)
Same issue here. Reading through the comments above it made me think: would it be possible to make when jnlp is first started through a web browser to save this jnlp to local Jenkins directory and automatically configure service to use this cached copy instead of requesting it from the server? This would make setting up slaves automatic again without altering security fix.