I'm confident the Java web start (JNLP) scenario does not require that you perform any other upgrade steps. I've used that technique for years across many Jenkins versions without ever performing any upgrade on the machine which invokes Java web start.
Since the "slave as a Windows service" seems to use JNLP as well, I'm reasonably confident that the upgrade is automatic in that scenario, just as it is automatic in the Java web start scenario. Mark Waite https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice%28require.NET2.0framework%29 >________________________________ > From: Vladimir Zak <zakvladi...@gmail.com> >To: jenkinsci-users@googlegroups.com >Sent: Saturday, January 5, 2013 12:47 PM >Subject: Re: Upgrade of Jenkins - is it necessary to upgrade slaves too? > >Hi, > >I have already read it but for running slave via Java web start and >then windows service there is no information about that. > >Thank you. > >zakyn > > > > >2013/1/5 Mark Waite <markwa...@yahoo.com>: >> It depends how you launch the slave. There is a good description on the >> wiki which can guide you. >> >> See >> https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds#Distributedbuilds-Differentwaysofstartingslaveagents >> >> Mark Waite >> >> ________________________________ >> From: zakyn <zakvladi...@gmail.com> >> To: jenkinsci-users@googlegroups.com >> Sent: Saturday, January 5, 2013 7:14 AM >> Subject: Upgrade of Jenkins - is it necessary to upgrade slaves too? >> >> Hello, >> >> I would like to upgrade my old Jenkins to the LTS Jenkins and I have a slave >> too. Should I anyhow upgrade the slave agent too or not? >> >> Thanks a lot. >> >> Zakyn >> >> > > >
