Closed smlambert closed 3 days ago
Would be handy to link to the release pipeline generator job in the Checklist (instead of having to go to release doc to find it)
Update release status template to include aarch64_alpine-linux where applicable
Update code freeze message from
With under a week to go until releases, we are entering a lockdown period for the master branches in the following repositories: github-release-scripts, containers, installer, and mirror-scripts. The temurin-build, ci-jenkins-pipelines and jenkins-helper master branches are still open for work, however the release branch will be under code-freeze management.
as it is not a 'lockdown period for master branches', but for the release branches.
It is not possible to dryrun jdk22u, as there is no jdk-22.0.2 upstream tags, and I don't feel we should artificially create a arbitrary "tag". I think we should probably enable for these Oracle managed releases, to be able to launch a release-pipeline "Release" type build using the HEAD "dev" branch rather than a tag...?
It is not possible to dryrun jdk22u, as there is no jdk-22.0.2 upstream tags, and I don't feel we should artificially create a arbitrary "tag". I think we should probably enable for these Oracle managed releases, to be able to launch a release-pipeline "Release" type build using the HEAD "dev" branch rather than a tag...?
Interesting, I’ve just manually kicked off a release-openjdk22-pipeline and it’s actually building HEAD of “dev” with a "version string" of the latest ga tag which is 22.0.1+8-ga I was expecting the testenv check to fail…but it hasn’t I think because scm_ref is “” So that will probably do, as it is building the very latest jdk-22.0.2 HEAD commits, but under a version string of jdk-22.0.1+8, which is probably fine as a dryrun
I did not get https://github.com/adoptium/aqa-tests/pull/5456 merged until after pipelines triggered, some tests may have been triggered without the excludes in place. Reruns should pick up the changes.
Some test jobs failed as the test gathering process was sent to a machine that could not complete the job. We should have worker labels on nodes that are safe for these jobs.
Text below from: https://github.com/adoptium/aqa-tests/issues/5444#issuecomment-2233270448
extended.perf
Failed when collecting artifacts via machine test-sxa-armv7l-ubuntu2004-odroid-2
[2024-07-17T06:00:38.100Z] Running on test-sxa-armv7l-ubuntu2004-odroid-2 in /ssd/jenkins/workspace/Test_openjdk21_hs_sanity.perf_x86-64_windows
...
[2024-07-17T06:04:49.333Z] Exception: hudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException
https://ci.adoptium.net/job/Test_openjdk21_hs_sanity.perf_x86-64_windows/159/consoleText
Scorecards make assumption that a -ga tag has dropped. There has been no -ga tag for jdk8u422, https://github.com/adoptium/jdk8u/tags, so our calculations / scores won't get generated (and when they do, we will have to adjust based on a mailing list email or when we finally decided to trigger off of jdk8u422-b05
The marketplace data repository had it's update action suspended due to inactivity in the repository.
Presumably this was notified by e-mail to some group (at Eclipse?) - it was only noticed by the project by chance. We need to receive such notifications and/or configure the repo to keep the actions alive longer.
Solaris AQA Pipeline failed due to issues with USE_TESTENV_PROPERTIES, the shell script it calls, does not work on solaris
https://github.com/adoptium/aqa-tests/blob/master/scripts/testenv/testenvSettings.sh
Falls out with the IF statement on line 5
Update checklist to use correct link for homebrew cask https://github.com/Homebrew/homebrew-cask/blob/master/Casks/t/temurin.rb
Same issue as previous releases, https://github.com/adoptium/temurin/issues/28#issuecomment-2077153603, where Release Notes do not show up on website even after a day of them being published to the binaries repo, https://adoptium.net/temurin/release-notes/?version=jdk-21.0.4+7
There are 2 mentions in checklist to check for JDK8 arm32 tags, one refers to Mercurial, is it outdated and if so, should be removed See the item that reads: "Check for presence of jdk8u aarch32 GA tag and mirror it Mercurial repo - Mirror job"
Update the link that is listed in this checklist item, since it doesn't exist.
"Consider updating the API as required via the relevant parts of the Adoptium API model constants. "
Unfortunately we missed a jdk8u Mac x64 "sign_installer" failure: https://adoptium.slack.com/archives/CLCFNV2JG/p1721905189045429?thread_ts=1721901821.714339&cid=CLCFNV2JG
This highlights the problem of always RED build pipelines, as test job failures are propagated...?
Propose: We should re-order the pipeline such that signInstaller, gpgSign and verifySigning stages are all done BEFORE running aqa-tests, if any of those 3 stages fail, we do not run aqa-tests. This then makes the failure very obvious to the release AQA triage. https://github.com/adoptium/ci-jenkins-pipelines/blob/69247d65158df1a49fdea5c797d57122d4b05c61/pipelines/build/common/openjdk_build_pipeline.groovy#L2215
Issue & PR to re-order: https://github.com/adoptium/ci-jenkins-pipelines/pull/1087
We should re-order the pipeline such that signInstaller, gpgSign and verifySigning stages
+1 as this would also save resources to not trigger testing at all in the cases where those stages fail
The generated dry-run Publish job link for "Point release" re-builds, does not add the adopt_build_number to the TAG parameter
Consider just adding all of the upcoming releases to the release calendar in 1 go and removing this item from the release checklist
Ensure the adoptium calendar is updated for the next cycle at a minimum
Mac homebrew cask updates process is not clear, especially for ".1" re-build updates, eg.https://github.com/Homebrew/homebrew-cask/pull/180691 Documentation not great if you've not done it before........?
Notes from aqa-tests triage:
JDK8
JDK17
JDK22
The new reduced size rerun feature in aqa-tests is great, really reduced time it took to triage tests.
Was great that @steelhead31 did all the installer items in the checklist. Wondering if there will be updates to that process before October.
Should we add the publish aqa-tests result taps tar to the checklist? Also somewhere to add the documents of how to do this?
Adam
Andrew
Shelley
Sophia
Other notes Already fixed: https://github.com/adoptium/temurin/issues/50#issuecomment-2237493875
Summary
A retrospective for all efforts surrounding the titular releases.
All community members are welcome to contribute to the agenda via comments below.
This will be a virtual meeting after the release, with at least a week of notice in the #release Slack channel.
On the day of the meeting we'll review the agenda and add a list of actions at the end.
Invited: Everyone.
Time, Date, and URL
Time: 3pm (GMT+1, UK), 10am (GMT -4, Ontario) Date: Wednesday, 31st of July URL: https://meet.google.com/tny-iobv-omt Phone: +44 20 3937 3489 and enter this PIN: 698 738 573# To view more phone numbers, click this link: https://tel.meet/tny-iobv-omt?hs=5
Details
Retrospective Owner Tasks (in order):
TLDR
Add proposed agenda items as comments below.