[JENKINS-54305] Oracle JDK 10 not available anymore - Oracle JDK 11 is not free

[jenkins-infra-bot]

The automatic installation of Tool JDK 10 failed today for us with a 404. It seems Oracle JDK 10 not available anymore at all. And Java 11 cannot be used in production due to new licences. No JDK 11 is available in Jenkins java.sun.com JDK Tool installer.

https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html

I guess the tool installer should be changed to use http://openjdk.java.net/projects/jdk/11/ (downloaded from http://jdk.java.net/11/).

Acceptance criteria

• a JDK 11 is proposed as download
• ideally, see if we can still propose JDK10,
• and JDK12

---

Originally reported by marcus_phi, imported from: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free

• status: Resolved
• priority: Critical
• component(s): jdk-tool-plugin
• label(s): java11, java11-compatibility, triaged
• resolution: Fixed
• resolved: 2021-05-10T13:44:47+00:00
• votes: 9
• watchers: 19
• imported: 20251215-193512

Raw content of original issue

The automatic installation of Tool JDK 10 failed today for us with a 404. It seems Oracle JDK 10 not available anymore at all. And Java 11 cannot be used in production due to new licences. No JDK 11 is available in Jenkins java.sun.com JDK Tool installer.

https://www.oracle.com/technetwork/java/javase/downloads/jdk11-downloads-5066655.html

I guess the tool installer should be changed to use http://openjdk.java.net/projects/jdk/11/ (downloaded from http://jdk.java.net/11/).

Acceptance criteria

	
a JDK 11 is proposed as download
	
ideally, see if we can still propose JDK10,
	
and JDK12

[jenkins-infra-bot]

olblak:

• Original comment link
• Raw content of original comment:

  I don't think that you wanted to open this issue on this project, INFRA is all about infrastructure running jenkins project.
  Is you issue related to https://github.com/jenkinsci/jdk-tool-plugin? 
  Maybe dnusbaum can help on this? 
  
  To give you an idea, on ci.jenkins.io, we set jdk11 to: 
  
  	
  https://download.java.net/java/ga/jdk11/openjdk-11_linux-x64_bin.tar.gz
  	
  https://download.java.net/java/ga/jdk11/openjdk-11_windows-x64_bin.zip
  
  
  

I don't think that you wanted to open this issue on this project, INFRA is all about infrastructure running jenkins project.
Is you issue related to https://github.com/jenkinsci/jdk-tool-plugin?
Maybe dnusbaum can help on this?

To give you an idea, on ci.jenkins.io, we set jdk11 to:

• https://download.java.net/java/ga/jdk11/openjdk-11_linux-x64_bin.tar.gz
• https://download.java.net/java/ga/jdk11/openjdk-11_windows-x64_bin.zip

[jenkins-infra-bot]

dnusbaum:

• Original comment link
• Raw content of original comment:

  Yes, Oracle's JDK 11 license change is problematic for most users.
  
  If I had time, I would like to switch the plugin to using OpenJDK builds from this page: https://jdk.java.net/archive/ (although that might not have the most current version of each release?). We would need to update the crawler to look in the right place, and change JDKInstaller.java to accommodate, but I do not think I will have any time to work on this in the near future.
  
  That said, the only reason this installation method exists in the first place is for backwards compatibility. It is unreliable and can break any time Oracle's website is updated (see JENKINS-47448 for an example of when this happened), and OpenJDK does not provide binary downloads for JDK 8 or older, so users building against old versions for whatever reason will be broken if we switch to OpenJDK. 
  
  My recommendation would be to install the JDK on your build agents in advance instead of installing it on-demand using Jenkins. If you really need to install it on-demand, then it is better to use something like the "Run a shell command installer" with a script that runs apt-get install openjdk-11-jdk or similar to make sure you get the latest updates.
  

Yes, Oracle's JDK 11 license change is problematic for most users.

If I had time, I would like to switch the plugin to using OpenJDK builds from this page: https://jdk.java.net/archive/ (although that might not have the most current version of each release?). We would need to update the crawler to look in the right place, and change JDKInstaller.java to accommodate, but I do not think I will have any time to work on this in the near future.

That said, the only reason this installation method exists in the first place is for backwards compatibility. It is unreliable and can break any time Oracle's website is updated (see JENKINS-47448">JENKINS-47448 for an example of when this happened), and OpenJDK does not provide binary downloads for JDK 8 or older, so users building against old versions for whatever reason will be broken if we switch to OpenJDK.

My recommendation would be to install the JDK on your build agents in advance instead of installing it on-demand using Jenkins. If you really need to install it on-demand, then it is better to use something like the "Run a shell command installer" with a script that runs apt-get install openjdk-11-jdk or similar to make sure you get the latest updates.

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  We had a discussion about this issue in Platform SIG. I have tentatively added it to the Java 11 EPIC for consideration.
  
  My proposal would be to rename the plugin to "Oracle JDK Installer" and to mark it as deprecated for now. I do not think there is a pressing issue to provide a ToolInstaller replacement for OpenJDK which also has weird distribution policies starting from Java 11. Maybe the best way is to add AdoptOpenJDK installer or something like that
  

We had a discussion about this issue in Platform SIG. I have tentatively added it to the Java 11 EPIC for consideration.

My proposal would be to rename the plugin to "Oracle JDK Installer" and to mark it as deprecated for now. I do not think there is a pressing issue to provide a ToolInstaller replacement for OpenJDK which also has weird distribution policies starting from Java 11. Maybe the best way is to add AdoptOpenJDK installer or something like that

[jenkins-infra-bot]

marcus_phi:

• Original comment link
• Raw content of original comment:

  I am quite OK with this not getting fixed. The main problem is really the confusion ('java.sun.com' in Installer name, no Java 11 appearing, Java 10 install failing, ...), not that there is no download installer available OOTB. It's simple to install the tool in another way.
  

I am quite OK with this not getting fixed. The main problem is really the confusion ('java.sun.com' in Installer name, no Java 11 appearing, Java 10 install failing, ...), not that there is no download installer available OOTB. It's simple to install the tool in another way.

[jenkins-infra-bot]

falcon:

• Original comment link
• Raw content of original comment:

  While I get your position guys, I think it's really a shame if that plugin disappears
  
  In my company, we have half a dozen of main projects, each one with its own rythm and most of all its one constraints. For example, for every installation or major upgrade in production of one of them, the whole software has to been checked (including third party librairies used, the embedeed JVM, ...) so it is unimaginable to change the JVM, even for a minor update, just because today is sunny
  
  Having this plugin, each team can specify, in its pipeline, what version of Java they want (8, 10, ...)
  
  Installing the JDK on the agent force builds to use it, and remove the choice to teams. Unless I am missing something ?
  

While I get your position guys, I think it's really a shame if that plugin disappears

In my company, we have half a dozen of main projects, each one with its own rythm and most of all its one constraints. For example, for every installation or major upgrade in production of one of them, the whole software has to been checked (including third party librairies used, the embedeed JVM, ...) so it is unimaginable to change the JVM, even for a minor update, just because today is sunny

Having this plugin, each team can specify, in its pipeline, what version of Java they want (8, 10, ...)

Installing the JDK on the agent force builds to use it, and remove the choice to teams. Unless I am missing something ?

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  > Installing the JDK on the agent force builds to use it, and remove the choice to teams. Unless I am missing something ?
  
  It depends on what you understand under "agent". For containers/images it is not a problem, they can be provisioned on-demand.For classic types of agents you are still able to install multiple Java Versions and then just use another ToolInstaller to set path, e.g. to a shared directory.
  
  > I think it's really a shame if that plugin disappears
  
  We welcome all contributions to the project. If somebody steps up and maintains the plugin, it will be a benefit to everyone.
  
   
  
   
  

> Installing the JDK on the agent force builds to use it, and remove the choice to teams. Unless I am missing something ?

It depends on what you understand under "agent". For containers/images it is not a problem, they can be provisioned on-demand.For classic types of agents you are still able to install multiple Java Versions and then just use another ToolInstaller to set path, e.g. to a shared directory.

> I think it's really a shame if that plugin disappears

We welcome all contributions to the project. If somebody steps up and maintains the plugin, it will be a benefit to everyone.

 

 

[jenkins-infra-bot]

falcon:

• Original comment link
• Raw content of original comment:

  > For containers/images it is not a problem
  
  you're right
  
  > For classic types of agents you are still able to install multiple Java Versions and then just use another ToolInstaller to set path, e.g. to a shared directory
  
  I have more this one in head. I can do this, but it's much more simpler to declare a tool in Jenkins tools configuration, provide a variable in my shared global pipeline lib, and let teams pick the one they want
  
  > We welcome all contributions to the project. If somebody steps up and maintains the plugin, it will be a benefit to everyone.
  
  I know how open source works  and be sure that every contribution I can do at my level, I do.
  
  Here I am a little bit lost ... For the crawler, can I open a PR on it ? It is Jenkins own INFRA, not (directly) used by jenkins installations. And about weird distribution policies, what is the problem ? If we fix the plugin to supports JDK 11, it is ok or not ?
  

> For containers/images it is not a problem

you're right

> For classic types of agents you are still able to install multiple Java Versions and then just use another ToolInstaller to set path, e.g. to a shared directory

I have more this one in head. I can do this, but it's much more simpler to declare a tool in Jenkins tools configuration, provide a variable in my shared global pipeline lib, and let teams pick the one they want

> We welcome all contributions to the project. If somebody steps up and maintains the plugin, it will be a benefit to everyone.

I know how open source works  and be sure that every contribution I can do at my level, I do.

Here I am a little bit lost ... For the crawler, can I open a PR on it ? It is Jenkins own INFRA, not (directly) used by jenkins installations. And about weird distribution policies, what is the problem ? If we fix the plugin to supports JDK 11, it is ok or not ?

[jenkins-infra-bot]

dnusbaum:

• Original comment link
• Raw content of original comment:

  
  Here I am a little bit lost ... For the crawler, can I open a PR on it ? It is Jenkins own INFRA, not (directly) used by jenkins installations. And about weird distribution policies, what is the problem ? If we fix the plugin to supports JDK 11, it is ok or not ?
  
  Yep, the crawler runs on Jenkins Infra, and it publishes this file, which is then downloaded by Jenkins instances which use it to know what JDK versions are available and what their download URLs are. I think you should be fine to open a PR against the crawler, although you would likely need to synchronize it with a PR to https://github.com/jenkinsci/jdk-tool-plugin, and depending on the changes required you might need to publish a new file instead of the old one so compatibility with old instances is not broken (for example if you switch to AdoptOpenJDK).
  

Here I am a little bit lost ... For the crawler, can I open a PR on it ? It is Jenkins own INFRA, not (directly) used by jenkins installations. And about weird distribution policies, what is the problem ? If we fix the plugin to supports JDK 11, it is ok or not ?

Yep, the crawler runs on Jenkins Infra, and it publishes this file, which is then downloaded by Jenkins instances which use it to know what JDK versions are available and what their download URLs are. I think you should be fine to open a PR against the crawler, although you would likely need to synchronize it with a PR to https://github.com/jenkinsci/jdk-tool-plugin, and depending on the changes required you might need to publish a new file instead of the old one so compatibility with old instances is not broken (for example if you switch to AdoptOpenJDK).

[jenkins-infra-bot]

falcon:

• Original comment link
• Raw content of original comment:

  Thanks dnusbaum will try 
  

Thanks dnusbaum will try

[jenkins-infra-bot]

brendanh:

• Original comment link
• Raw content of original comment:

  JDK10 is still available, but the plugin now has the wrong URL for it.  Per the issue I've just opened, first part of the URL should be:
  
  http://download.oracle.com/otn
  instead of:
  http://download.oracle.com/otn-pub
  
  Can we get this corrected?
  

JDK10 is still available, but the plugin now has the wrong URL for it. Per the issue I've just opened, first part of the URL should be:

http://download.oracle.com/otn
instead of:
http://download.oracle.com/otn-pub

Can we get this corrected?

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  > Can we get this corrected?
  
   
  
  AFAICT https://github.com/jenkins-infra/crawler/blob/master/jdk.groovy#L27-L42 needs to be corrected. Somebody needs to propose a PR against this repo and then to test it
  

> Can we get this corrected?

 

AFAICT https://github.com/jenkins-infra/crawler/blob/master/jdk.groovy#L27-L42 needs to be corrected. Somebody needs to propose a PR against this repo and then to test it

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  I think we need to do something about that for the GA release
  

I think we need to do something about that for the GA release

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  Restore JDK runner jenkins-infra/crawler#79 removes listing of Java 10 in the tool installer
  

jenkins-infra/crawler#79 removes listing of Java 10 in the tool installer

[jenkins-infra-bot]

batmat:

• Original comment link
• Raw content of original comment:

  We are most probably not going to be able to propose Oracle JDK anymore for automated downloads after the crawlers. People willing to still do that will be able to do it on themselves.
  I think the remaining question is to decide if we use https://openjdk.java.net/ or AdoptOpenJDK. From a licensing perspective, I think this is very similar if not the same. 
  We'll probably decide also depending on the easiness using one or the other.
  

We are most probably not going to be able to propose Oracle JDK anymore for automated downloads after the crawlers. People willing to still do that will be able to do it on themselves.
I think the remaining question is to decide if we use https://openjdk.java.net/ or AdoptOpenJDK. From a licensing perspective, I think this is very similar if not the same.
We'll probably decide also depending on the easiness using one or the other.

[jenkins-infra-bot]

oleg_nenashev:

• Original comment link
• Raw content of original comment:

  batmatHave you considered my proposal in Restore JDK runner jenkins-infra/crawler#79 (comment) ? Closing this one and creating new one for JDK 11?
  

batmatHave you considered my proposal in jenkins-infra/crawler#79 (comment) ? Closing this one and creating new one for JDK 11?