The change is trivial but will remove support for OpenJ9 builds. Should we just do a release of the plugin including a note about removing OpenJ9?

IBM has announced support for OpenJ9, calling it Semeru, and making binaries available for download.

As I see it, there are two options:

• either enhance this plugin to support both endpoints, retaining the existing flexibility to choose from Hotspot/Openj9 aka Temurin / Semeru (.. who chooses these names?)
• or, deprecate this plugin and replace with two plugins, one each for Temurin / Semeru.

My preference is for a single plugin. This could also be extended to include Azul binaries or Microsoft build JDK and others.

This could be done hard-coded or via an option in the Global Configuration to add user-configurable/selectable locations.

The problem is more in the crawler script, than in the plugin:
https://github.com/jenkins-infra/crawler/blob/master/adoptopenjdk.groovy

However, the migration seems not too hard:
https://api.adoptopenjdk.net/migration.html

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.