[RELEASE] New release for 2025-05-27

[krisstern]

A new release is being scheduled.
Release manager: @krisstern

Note

For tasks that don't have a specific script, i.e. tasks 2, 4, 5, 7, and 10, run ./bom-release-issue-complete-task.sh <task number> to check the box off without having to manually edit the issue.

Release progress

• 1. makes sure the CRON expression to run the job is appropriate for the release date
  • line to check in the Jenkinsfile, time is UTC.
• 2. run ./bom-lock-master.sh before the job runs
• 3. wait to verify that job started at ci.jenkins.io
• 4. run ./bom-release-issue-job-running.sh <buildNumber>
  • Example: ./bom-release-issue-job-running.sh 1234
• 5. wait for build to make it through the prep stage then (typically) take a 1.5-2 hr break
• 6. (LOOP) if there are any failures, fix until everything is successful
• 7. run ./bom-run-cd-workflow.sh
  • wait for the release process to complete
  • this takes 7-8 minutes
• 8. manually edit the auto-generated release notes
  • remove <!-- Optional: add a release summary here -->
  • remove <details>
  • remove <summary>XYZ changes</summary>
  • remove </details>
• 9. run ./bom-release-issue-add-release-comment.sh
• 10. run ./bom-unlock-master.sh
• 11. verify that the branch is unlocked
• 12. run ./bom-release-issue-close.sh

[krisstern]

https://ci.jenkins.io/job/Tools/job/bom/job/master/4588/

[krisstern]

Currently trying to get #5084 merged before resuming work on this release.

[krisstern]

https://ci.jenkins.io/job/Tools/job/bom/job/master/4591/

[krisstern]

Currently trying to get #5086 merged before resuming work on this release.

[krisstern]

https://ci.jenkins.io/job/Tools/job/bom/job/master/4594/

[MarkEWaite]

Thanks so much for being the release lead this week @krisstern ! I see a test failure locally when I run the command:

LINE=weekly PLUGINS=kubernetes-credentials-provider TEST=KubernetesCredentialsProviderTest#startWatchingForSecrets bash ./local-test.sh

That test failure matches with a test failure on the full-tests run in 4594

That test failure is resolved when I revert the upgrade of Jackson 2 API plugin from 2.18.3-402.v74c4eb_f122b_2 to 2.19.0-404.vb_b_0fd2fea_e10.

As far as I can tell, the issue is related to class loading in the tests of the Kubernetes Credentials Provider plugin. I think that we should proceed with the plugin BOM release by excluding the failing tests of that plugin.

• Test Kubernetes Credentials Provider plugin update #5088

Pull request to duplicate the issue has been submitted to the plugin as:

• Confirm additional test dependency does not cause test failures kubernetes-credentials-provider-plugin#115

[MarkEWaite]

The Blue Ocean plugin failure seems to have a different root cause. It fails locally for me when I run:

LINE=weekly PLUGINS=blueocean-bitbucket-pipeline TEST=BitbucketCloudScmTest#getBitbucketScm bash ./local-test.sh

The revert of Jackson 2 API 2.19.0 will be necessary for a release, but it looks like it won't be sufficient. More investigation soon.