|
||||||||
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-16346) Upgrade to Jenkins ver. 1.499 breaks master/slave connection
vasilena.tren...@softwareag.com (JIRA) Tue, 15 Jan 2013 05:47:01 -0800
- [JIRA] (JENKINS-16346) Upgrade to J... vasilena.tren...@softwareag.com (JIRA)
- [JIRA] (JENKINS-16346) Upgrade... vasilena.tren...@softwareag.com (JIRA)
- [JIRA] (JENKINS-16346) Upgrade... alexlomba...@java.net (JIRA)
- [JIRA] (JENKINS-16346) Upgrade... s.sog...@gmail.com (JIRA)
- [JIRA] (JENKINS-16346) Upgrade... vasilena.tren...@softwareag.com (JIRA)
- [JIRA] (JENKINS-16346) Upgrade... jgl...@cloudbees.com (JIRA)
I will try both options now but will hold off that version for the moment![]()
If I have to explicitly pass -jnlpCredentials username:password then I guess Jenkins needs to generate the proper command line when configuring the slaves. I mean those:
Run from slave command line:
javaws http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp
Or if the slave is headless:
java -jar slave.jar -jnlpUrl http://bambpmsauto.eur.ad.sag:8080/computer/vmbam04.eur.ad.sag/slave-agent.jnlp
We have quite a lot of slaves and it will take a while to go tru all of them for reconfiguration![]()