Add jdk21 to build health report

[adamfarley]

No description provided.

[github-actions]

Thank you for creating a pull request!

Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).

Code Quality and Contributing Guidelines

If you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before.

Tests

Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation.

In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post run tests on this PR.
If you are not an admin, please ask for one's attention in #infrastructure on Slack or ping one here.
To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,20"

[adamfarley]

Test run here: https://ci.adoptium.net/job/nightlyBuildAndTestStats_temurin/1059/

EDIT: Failed because the call to "https://api.adoptium.net/v3/assets/feature_releases/21/ea" failed due to there being nothing there. Possibly because we've never released jdk21. I wonder how we've fetched this data for previous jdk versions prior to their first release. Will ask on #build slack channel.

Update: Known issue. Have reverted the healthcheck report generator job to use the master branch again, and I've asked John for insights on Slack:

• Issue link
• Slack chat link

Update: Solved! Good job John. Re-ran the health check job here and it successfully generated jdk21 output here. So we're ready for reviews.

[steelhead31]

LGTM

[sxa]

Can we make sure that this part of the process is documented in https://github.com/adoptium/temurin-build/blob/master/RELEASING.md#openjdk-new-major-release-process - probably using a link to this PR as an example.

[adamfarley]

Can we make sure that this part of the process is documented in https://github.com/adoptium/temurin-build/blob/master/RELEASING.md#openjdk-new-major-release-process - probably using a link to this PR as an example.

Sure. I'll hold off until John Oliver has replied to this Slack message with the details of his changes to api.adoptium.net.

[sxa]

From the thread it seems that https://github.com/adoptium/api.adoptium.net/blob/bda17356dae38e4a36a2aa2aef9bec3b5e9e4275/adoptium-models-parent/adoptium-api-v3-models/src/main/kotlin/net/adoptium/api/v3/models/Versions.kt#L5 needs to be updated too so that should be done and added to the docs as well (The immediate fix that was applied to resolve this was to override the java LATEST_JAVA_VERSION property in the API instead of updating that file)

[andrew-m-leonard]

lgtm

[sxa]

API change PR: adoptium/api.adoptium.net#578

[sxa]

Approving on the basis that the documentation gets done, as that will need to be in a different repository anyway so will not be part of this PR.

[adamfarley]

Note: The docs change mentioned above was carried out here: adoptium/temurin-build#3360