[JIRA] [remoting] (JENKINS-32036) Slave disconnects after moving the windows clock forward

[cameron.spen...@caseware.com (JIRA)]

Title: Message Title

Cam Spencer commented on JENKINS-32036   Re: Slave disconnects after moving the windows clock forward Hey James Nord, I'm not sure what version the slave.jar is, but I can guarantee it's not up to date. It probably hasn't been touched in a couple of years. As per https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds we never really concerned ourselves with using the latest slave.jar. "Updating slave.jar Technically speaking, in this set up you should update slave.jar every time you upgrade Jenkins to a new version. However, in practice slave.jar changes infrequently enough that it's also practical not to update until you see a fatal problem in start-up." I'll make sure to try this with a new slave.jar (Currently our Jenkins is 1.639) and update this bug with the results. You're correct that the clock change is happening on the slave. None of our tests run on the master. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.