JDK patch upgrade campaign (January 2025)

[smerle33]

Service(s)

cert.ci.jenkins.io, ci.jenkins.io, infra.ci.jenkins.io, release.ci.jenkins.io, trusted.ci.jenkins.io, weekly.ci.jenkins.io

Summary

See previous issue: #4058

As per https://www.java.com/releases/, all JDKs we are using (8, 11, 17 and 21) received a patch upgrade the 21 january 2025
This issue tracks the steps required to upgrade all JDKs across the platform for our developers.

The scope is for JDK tools, Jenkins agent JDKs and Jenkins controllers JDKs. Note that we accept a patch-difference between controller and agent JDks.

New JDK versions:

• 21.0.6, Available on adoptium: https://github.com/adoptium/temurin21-binaries/releases/tag/jdk-21.0.6%2B7
• 17.0.14, Available on adoptium: https://github.com/adoptium/temurin17-binaries/releases/tag/jdk-17.0.14%2B7
• 11.0.26, Available on adoptium: https://github.com/adoptium/temurin11-binaries/releases/tag/jdk-11.0.26%2B4
• 8u442, Available on adoptium: https://github.com/adoptium/temurin8-binaries/releases/tag/jdk8u442-b06

Elements to be updated:

• Jenkins controller images:
  • Weekly 2.496 (February 4 2025) use the news JDKs (for infra.ci and weekly.ci controllers) https://github.com/jenkinsci/docker/releases/tag/2.496
  • Next LTS 2.492.1 (February 5 2025) use the new JDKs (for all the other controllers) https://github.com/jenkinsci/docker/releases/tag/2.492.1
• Jenkins agent images:
  • Packer Image, aka. "all-in-one" images for Linux VM agents, Windows VM agents and most of the Linux container agents.
    • JDK8: Bump JDK8 version to 8u442-b06 packer-images#1686
    • JDK11: Bump JDK11 version to 11.0.26+4 packer-images#1683
    • JDK17: Bump JDK17 version to 17.0.14+7 packer-images#1684
    • JDK21: Bump JDK21 version to 21.0.6+7 packer-images#1685
    • Release: https://github.com/jenkins-infra/packer-images/releases/tag/2.25.0 - https://github.com/jenkins-infra/packer-images/releases/tag/2.26.0
    • Deployment: Bump agent templates for infra.ci.jenkins.io (packer-image 2.26.0) kubernetes-management#6177 and Bump Packer Agent Templates (All-In-One) Version to 2.26.0 jenkins-infra#3858
  • Windows Container agent
    • JDK8: Bump JDK8 version to jdk8u442-b06 docker-inbound-agents#205
    • JDK11: Bump JDK11 version to jdk-11.0.26+4 docker-inbound-agents#202
    • JDK17: Bump JDK17 version to jdk-17.0.14+7 docker-inbound-agents#203
    • JDK21: Bump JDK21 version to jdk-21.0.6+7 docker-inbound-agents#204
    • Deployment: Bump non-packer container agent templates version on all controllers jenkins-infra#3849
  • Web-builder aka. "docker-builder" Bump Jenkins Inbound Agent Version to 3283.v92c105e0f819-8 docker-builder#282
  • Packaging aka. "docker-packaging" Bump Jenkins inbound-agent version to 3283.v92c105e0f819-8 docker-packaging#152 and Bump JDK17 version to 17.0.14_7 docker-packaging#153
• JDK tools:
  • Puppet-managed controllers:
    • ci.jenkins.io
    • trusted.ci.jenkins.io
    • cert.ci.jenkins.io
    • PRs:
      • JDK8: Bump JDK8 version (Jenkins tools) on all controllers to 8u442-b06 jenkins-infra#3841
      • JDK11: Bump JDK11 version (Jenkins tools) on all controllers to 11.0.26+4 jenkins-infra#3851
      • JDK17: Bump JDK17 version (Jenkins tools) on all controllers to 17.0.14+7 jenkins-infra#3843
      • JDK21: Bump JDK21 version (Jenkins tools) on all controllers to 21.0.6+7 jenkins-infra#3842
  • Kubernetes-managed controllers:
    • infra.ci.jenkins.io
      • JDK8: Bump JDK8 version (Jenkins tools) on all controllers to jdk8u442-b06 kubernetes-management#6141
      • JDK11: Bump JDK11 version (Jenkins tools) on all controllers to jdk-11.0.26+4 kubernetes-management#6147
      • JDK17: Bump JDK17 version (Jenkins tools) on all controllers to jdk-17.0.14+7 kubernetes-management#6148
      • JDK21: Bump JDK21 version (Jenkins tools) on all controllers to jdk-21.0.6+7 kubernetes-management#6142

Reproduction steps

No response

[dduportal]

Update: we are blocked on the release of the packer image due to (JDK unrelated) AWS Windows 2019 issue: jenkins-infra/packer-images#1702

[smerle33]

trusted.ci.jenkins.io has a manual workaround but we consider it as updated see #4500 (comment)