adoptopenjdk.net will stop getting new builds this july, so approx. 2 months from now. It would be really great to update this plugin before it happens.

The Jenkins platform SIG stopped support of OpenJ9 and closed issues related to OpenJ9 several months ago. We don't have enough people in the platform SIG that are interested in OpenJ9 for it to be a viable Jenkins platform. It was used briefly to support JDK 8 on s390x. Since JDK 8 will soon be end of life for the Jenkins project, we use the hostspot virtual machines for JDK 11 and JDK 17 on s390x.

markewaite , I thought this Jira was to ensure the "AdoptOpenJDK installer plugin" continue to be able to retrieve Temurin JDK binaries from adoptium.net, following the announcement that "AdoptOpenJDK is moving to the Eclipse Foundation"

That plugin provides similar functionality to the Oracle Java SE Development Kit Installer plugin, providing specific JDK to Jobs, which is independent of the Java version running Jenkins platform itself.

My remark was aligned with mmchr's remark that OpenJ9 JDK would no longer be available from AdoptOpenJDK and instead be served as Semeru from IBM.

However while Mads remark was to clarify (ie: document) OpenJ9 would no longer be available (ie: only Temurin, from Adoptium), my expressed preference was to enhance the "OpenJDK" plugin to support installing multiple flavors of JDK from the most popular providers, at least to continue with the OpenJ9 retrieval from IBM. The the alternative will be a proliferation multiple provider specific JDK installer plugins.

my expressed preference was to enhance the "OpenJDK" plugin to support installing multiple flavors of JDK from the most popular providers, at least to continue with the OpenJ9 retrieval from IBM. The the alternative will be a proliferation multiple provider specific JDK installer plugins.

I think that is a decent idea, but I am not aware of anyone who has committed to implementing it. If nobody implements this, you can consider opening a pull request to make your expressed preference a reality.

Is it just me or is this plugin completely unusable now?

mwinfield I'm using the most recent pre-release build of the Temurin improvement pull request to this plugin successfully. Can you describe in more detail what makes the plugin "completely unusable" for you?

All of the old archived versions from AdoptOpenJDK have been removed as an option from the automatically installed from adoptopenjdk.net option. All the versions that are left are not being installed on build nodes so we are having to move everything to install from .zip/.tar

It seems to be related to AdoptOpenJDK moving release to Adoptium. Something changed last week on that end as we saw one Jenkins instance impacted a couple days before our other Jenkins instance also break. It looked like one received an updated listed from the site before the other possibly due to CDN.

The crawler that identifies packages for the plugin was updated last week . It no longer delivers Java releases that are not supported by Adoptium (like Java 9, Java 10, Java 12).

If you need those old versions, then download from zip/tar is the best choice.

Download from zip/tar is the preferred choice even for available versions, since it is better to locally download the 100+ MB zip or tar file than to request it from Adoptium over the public internet.

Fixed in jenkinsci/adoptopenjdk-plugin#23. Released in 1.5.