> On 4. Dec 2017, at 17:53, Steve K <steve.kerxha...@carestream.com> wrote: > > We're not using a JDK tool in our builds. > > This has become a huge pain. I can see from your link that Oracle is > probably to blame, but I don't see where I can change Jenkins' mind about > what JDK to look for. > > Thanks again.
There's likely a single JDK configured in Manage Jenkins ยป Global Tool Configuration with an auto-installer that downloads from Oracle (the label might still say java.sun.com). If so, your options are: - Remove the tool. - Remove the auto-installer for the JDK that downloads it from the Oracle site. - Add a second tool version, which makes the per-job option explicit. Any jobs relying on the existing one set up automatically will fail until you explicitly configure one. - Override the path to the JDK on the agent your builds are failing on, this should override the unavailable auto installer. -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/714B2AB3-02A6-4993-8B8B-DE0270B95CBF%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
