[RELEASE] New release for 2026-01-09

[alecharp]

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

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

[alecharp]

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

[alecharp]

aws-global-configuration plugin failed because of dependency resolution error

Failed to read artifact descriptor for io.jenkins.plugins:oss-symbols-api:jar:356.v2da_d59a_3742b_

09:38:12  	Caused by: The following artifacts could not be resolved: io.jenkins.plugins:oss-symbols-api:pom:356.v2da_d59a_3742b_ (absent): Could not transfer artifact io.jenkins.plugins:oss-symbols-api:pom:356.v2da_d59a_3742b_ from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local: Temporary failure in name resolution

09:38:12  Failed to read artifact descriptor for io.jenkins.plugins.aws-java-sdk2:aws-java-sdk2-core:jar:2.31.63-54.vcf1e5a_c56c49

09:38:12  	Caused by: The following artifacts could not be resolved: io.jenkins.plugins.aws-java-sdk2:aws-java-sdk2-core:pom:2.31.63-54.vcf1e5a_c56c49 (absent): Could not transfer artifact io.jenkins.plugins.aws-java-sdk2:aws-java-sdk2-core:pom:2.31.63-54.vcf1e5a_c56c49 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for org.jenkins-ci.plugins:aws-credentials:jar:248.v78a_dcfc9db_ff

09:38:12  	Caused by: The following artifacts could not be resolved: org.jenkins-ci.plugins:aws-credentials:pom:248.v78a_dcfc9db_ff (absent): Could not transfer artifact org.jenkins-ci.plugins:aws-credentials:pom:248.v78a_dcfc9db_ff from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for org.jenkins-ci.plugins:structs:jar:350.v3b_30f09f2363

09:38:12  	Caused by: The following artifacts could not be resolved: org.jenkins-ci.plugins:structs:pom:350.v3b_30f09f2363 (absent): Could not transfer artifact org.jenkins-ci.plugins:structs:pom:350.v3b_30f09f2363 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for commons-logging:commons-logging:jar:1.3.4

09:38:12  	Caused by: The following artifacts could not be resolved: commons-logging:commons-logging:pom:1.3.4 (absent): Could not transfer artifact commons-logging:commons-logging:pom:1.3.4 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for commons-codec:commons-codec:jar:1.17.1

09:38:12  	Caused by: The following artifacts could not be resolved: commons-codec:commons-codec:pom:1.17.1 (absent): Could not transfer artifact commons-codec:commons-codec:pom:1.17.1 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for io.jenkins.plugins:jaxb:jar:2.3.9-133.vb_ec76a_73f706

09:38:12  	Caused by: The following artifacts could not be resolved: io.jenkins.plugins:jaxb:pom:2.3.9-133.vb_ec76a_73f706 (absent): Could not transfer artifact io.jenkins.plugins:jaxb:pom:2.3.9-133.vb_ec76a_73f706 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for io.jenkins.plugins:joda-time-api:jar:2.14.0-127.v7d9da_295a_d51

09:38:12  	Caused by: The following artifacts could not be resolved: io.jenkins.plugins:joda-time-api:pom:2.14.0-127.v7d9da_295a_d51 (absent): Could not transfer artifact io.jenkins.plugins:joda-time-api:pom:2.14.0-127.v7d9da_295a_d51 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for org.jenkins-ci.plugins:jackson2-api:jar:2.18.3-402.v74c4eb_f122b_2

09:38:12  	Caused by: The following artifacts could not be resolved: org.jenkins-ci.plugins:jackson2-api:pom:2.18.3-402.v74c4eb_f122b_2 (absent): Could not transfer artifact org.jenkins-ci.plugins:jackson2-api:pom:2.18.3-402.v74c4eb_f122b_2 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for io.jenkins:configuration-as-code:jar:1963.v24e046127a_3f

09:38:12  	Caused by: The following artifacts could not be resolved: io.jenkins:configuration-as-code:pom:1963.v24e046127a_3f (absent): Could not transfer artifact io.jenkins:configuration-as-code:pom:1963.v24e046127a_3f from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for io.jenkins.configuration-as-code:test-harness:jar:1963.v24e046127a_3f

09:38:12  	Caused by: The following artifacts could not be resolved: io.jenkins.configuration-as-code:test-harness:pom:1963.v24e046127a_3f (absent): Could not transfer artifact io.jenkins.configuration-as-code:test-harness:pom:1963.v24e046127a_3f from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for org.mockito:mockito-core:jar:5.19.0

09:38:12  	Caused by: The following artifacts could not be resolved: org.mockito:mockito-core:pom:5.19.0 (absent): Could not transfer artifact org.mockito:mockito-core:pom:5.19.0 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for org.jenkins-ci.main:jenkins-core:jar:2.479.3

09:38:12  	Caused by: The following artifacts could not be resolved: org.jenkins-ci.main:jenkins-core:pom:2.479.3 (absent): Could not transfer artifact org.jenkins-ci.main:jenkins-core:pom:2.479.3 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for org.jenkins-ci.main:jenkins-war:war:2.479.3

09:38:12  	Caused by: The following artifacts could not be resolved: org.jenkins-ci.main:jenkins-war:pom:2.479.3 (absent): Could not transfer artifact org.jenkins-ci.main:jenkins-war:pom:2.479.3 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for org.jenkins-ci.main:jenkins-test-harness:jar:2488.v0c38b_4e6b_cfa_

09:38:12  	Caused by: The following artifacts could not be resolved: org.jenkins-ci.main:jenkins-test-harness:pom:2488.v0c38b_4e6b_cfa_ (absent): Could not transfer artifact org.jenkins-ci.main:jenkins-test-harness:pom:2488.v0c38b_4e6b_cfa_ from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for org.jenkins-ci:test-annotations:jar:1.5

09:38:12  	Caused by: The following artifacts could not be resolved: org.jenkins-ci:test-annotations:pom:1.5 (absent): Could not transfer artifact org.jenkins-ci:test-annotations:pom:1.5 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for org.junit.jupiter:junit-jupiter:jar:5.13.4

09:38:12  	Caused by: The following artifacts could not be resolved: org.junit.jupiter:junit-jupiter:pom:5.13.4 (absent): Could not transfer artifact org.junit.jupiter:junit-jupiter:pom:5.13.4 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

09:38:12  Failed to read artifact descriptor for org.junit.vintage:junit-vintage-engine:jar:5.13.4

09:38:12  	Caused by: The following artifacts could not be resolved: org.junit.vintage:junit-vintage-engine:pom:5.13.4 (absent): Could not transfer artifact org.junit.vintage:junit-vintage-engine:pom:5.13.4 from/to artifact-caching-proxy (http://artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local:8080/): artifact-caching-proxy.artifact-caching-proxy.svc.cluster.local

Still investigating ssh-steps

[alecharp]

There is a problem along the way of jenkinsci/plugin-pom#1286. Pinning ssh-steps to previous release (reverting 7502e7c basically) does nothing.
Locally, when running local-test.sh with Java 17 setup, nothing works.

[alecharp]

I tried to not use local-test.sh but actually using what the Jenkinsfile is doing:

• call prep.sh with Java 21 setup, providing LINEZ environment variable to 2.504.x
• call pct.sh with Java 17 setup, providing LINE to 2.504.x and PLUGINS to ssh-steps.

This reports testing the plugin against Jenkins Core 2.545 (which it shouldn't) and it doesn't fail.

[alecharp]

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

[alecharp]

markdown-formatter plugin issue related to GitHub limitation

13:16:58  + exec java -Dorg.jenkins.tools.test.hook.JenkinsTestHarnessHook2.enabled -jar target/pct.jar test-plugins --war /home/jenkins/agent/workspace/Tools_bom_master/target/megawar-weekly.war --include-plugins markdown-formatter --working-dir /home/jenkins/agent/workspace/Tools_bom_master/target/pct-work -Dmaven.test.failure.ignore=true -Dsurefire.rerunFailingTestsCount=1 -DforkCount=.75C -Dsurefire.excludesFile=/home/jenkins/agent/workspace/Tools_bom_master/excludes.txt

13:16:58  2026-01-09 12:16:58.334+0000 [id=1]	INFO	o.j.tools.test.util.WarExtractor#getPlugin: Extracting metadata for markdown-formatter

13:16:58  2026-01-09 12:16:58.389+0000 [id=1]	INFO	o.j.t.t.m.h.PluginCompatTesterHooks#runHooks: Running hook: org.jenkins.tools.test.hook.TagValidationHook for Markdown Formatter

13:16:58  2026-01-09 12:16:58.389+0000 [id=1]	INFO	o.j.t.test.PluginCompatTester#testPlugins: Starting plugin tests on core version 2.545

13:16:58  2026-01-09 12:16:58.389+0000 [id=1]	INFO	o.j.t.test.PluginCompatTester#cloneImpl: Checking out from Git repository https://github.com/jenkinsci/markdown-formatter-plugin at ab3dea1413aff836d3c3ad68c41214fe2a273e55

13:17:18  org.jenkins.tools.test.exception.PluginSourcesUnavailableException: git fetch https://github.com/jenkinsci/markdown-formatter-plugin ab3dea1413aff836d3c3ad68c41214fe2a273e55 failed with exit status 128: fatal: unable to access 'https://github.com/jenkinsci/markdown-formatter-plugin/': Could not resolve host: github.com

[alecharp]

Here is what I use to try to reproduce locally the problem with ssh-steps

mise use --env local java@temurin-21
LINEZ="2.504.x" SAMPLE_PLUGIN_OPTS="-Dtest=InjectedTest -P2.504.x" bash prep.sh

mise use --env local java@temurin-17
LINE="2.504.x" PLUGINS=ssh-steps bash pct.sh

And this doesn't trigger the problem we can see on the CI.

[alecharp]

@MarkEWaite @krisstern @gounthar @darinpope Do you have any idea?

local-test.sh script uses the same JVM for prep.sh and pct.sh when in the Jenkinsfile, because we are not testing weekly, PCT is ran with Java 17 (expected). But the plugin (ssh-steps) complains that it is not in the required JVM version range.

It could have been related to jenkinsci/plugin-pom#1290 (which ssh-steps plugin doesn't have) but I would be able to reproduce locally the problem is that was it. And wouldn't it also fail on the other branches then (because of https://github.com/jenkinsci/bom/blob/master/Jenkinsfile#L115)?

I could blindly pin the plugin in bom-2.528.x/pom.xml to the previous version (which still uses parent-pom 5.28) but it would be just a wild guess at this point.

[krisstern]

The error stack trace looks exactly like the one I saw for #6198 in https://ci.jenkins.io/job/Tools/job/bom/job/PR-6198/1/ before

[MarkEWaite]

@MarkEWaite @krisstern @gounthar @darinpope Do you have any idea?

If I revert the parent pom upgrade eeaa672 and the ssh-steps upgrade 7502e7c. , then I'm able to run

git clean -xffd && LINE=2.504.x PLUGINS=ssh-steps TEST=InjectedTest bash ./local-test.sh

If I only revert one of those two commits, then that command fails

[alecharp]

@MarkEWaite are you using Java 17 or 21? prep (first call of local-test) is built with Java 21 on CI. Only PCT is ran with Java 17.

I'll revert those two commits but I think (no proof) that we need ssh-steps to be release with the newest version of parent-pom, which doesn't require Java 21.

[MarkEWaite]

@MarkEWaite are you using Java 17 or 21?

Using Java 17.0.17 for that test