|
||||||||
|
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 Alben,
I recently upgraded from 1.491 to 1.504 and it caused issues with communication to the slave.
in 1.498 there was a security update for encrypting configuration data etc. : https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04
This means you have to re-key all your configuration files (see your Manage Jenkins page of your installation).
I also had to replace the slave.jar, and add the "-secret xxxxxxxxxxxxxxx " option to the jenkins-slave.xml configuration on the slave ( where xxxx is the secret token).
These can both be obtained from the manage nodes configuration page. After restarting the Node and Master they both connected together OK.
Cheers,
Josh