manually installed JDK disappears on slave

[erw.p...@gmail.com]

I have a windows slave and I have both auto installed versions of java 1.8.0_60 as well as a manual install.  I do this because the version number plugin does not work with the auto install.  I have noticed that periodically, the manual installed version get uninstalled for some reason.  This windows server is only used as a slave and nothing else runs on it.  Is it possible that the auto installation is somehow trashing the manual install? Is it possible that java does not like to different versions of the same JDK on the same server  ... one under the jenkins tools and one under the manual installation?

Has anybody else experienced this before?

Note: I am running the latest LTS release 1.609.3

[Baptiste Mathus]

Do you mean you're overwriting the automated JDK installation with another one?
If so, then even if I'm not absolutely sure Jenkins has code to revert to the pristine version, there's a better/cleaner way to achieve your need IMO.

When configuring the JDK globally, don't use the automated installer. Use the alternative where you can specify the URL of a custom zip (your custom JDK).
Then on any slave Jenkins will download and install your custom version from the configure URL.

HTH
Cheers

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7c847d84-68d9-4ae1-a260-4e0705a0035f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.