Platform SIG October 22, 2024

Community
, , ,
1

Attending:

Agenda:

  • End of support for Java 11
    • Container repo for controller repo has dropped Java 11
    • Weekly 2.463 dropped support for Java 11.
    • Jenkins LTS 2.479.1 will drop support for Java 11 when it releases on 30 Oct 2024.
    • When should agent containers stop updates for Java 11?
      • Mark proposed to drop it last week
      • There are no security updates for Jenkins LTS versions before 2.479.1 once released on 30 Oct 2024.
      • Jenkins agents require a JDK that has the same major version as the controller or a greater JDK major version than the controller JVM.
        • After 30 Oct 2024, there will be no supported configuration where Java 11 agents run.
    • New version of remoting will be released soon, and should not support JDK11 anymore, and we could then deliver the new version of the agents with JDK17 only
      • Damien will trigger the release of the new remoting
  • Container image updates for the Jenkins controller
    • LTS
    • Weeklies (2.481 and 2.482)
      • Bump plugin manager to 2.13.2
      • Bump Debian Bookworm Linux Version to 20241016
  • Container image updates for Jenkins agents
    • No new release for the SSH agent
    • No new release for the docker-agent
  • Releasing a new docker image for the agents
    • Damien will teach us at the end of the meeting
  • Work in progress on images:
  • The Spring project made an end of life announcement - JENKINS-68698
    • Key milestones in the Spring Security 6.x upgrade
      • File upload 2.x in Jenkins weekly 2.459 (no issues reported)
      • Require Java 17 in Jenkins weekly 2.463 June 18, 2024 (see dev list)
      • Jetty 12 + EE 8 in Jenkins weekly 2.472 August 13, 2024
      • Jetty 12 + EE 9 + Spring Security 6.x in Jenkins weekly - 2.475
      • Jetty 12 + EE 9 + Spring Security 6.x in Jenkins weekly - 2.479.1 - 30 Oct 2024
  • 2+2+2 Java Support Plan
  • New JDK versions
    • 21.0.5-tem
    • 17.0.13-tem
    • I did not see any automatic PR: Bruno can’t see clearly :wink:
    • S390x is not available yet, that’s why the PRs did not fire
    • Ubi9 script does not work anymore
      • The script will be available
  • Jnlp-agent-jdk8
    • Inbound examples with tools, like maven…
    • Haven’t been updated in years
    • Risky to use
    • Built and deployed daily
      • It was expected, as they don’t have a deployment poilcy, it’s always latest version
      • They began to fail recently
    • What could we do?
      • Release one last version of JDK8 and JDK11 and pin to the latest remoting version for JDK8 and JDK11
      • Upgrade the images to JDK17?
      • Just archive the repo?
  • RISC-V status
    • We started the MILK-V Pioneer machine, running (unfortunately) Fedora 38
    • Jenkins LTS 2.462.3 runs without a glitch thanks to the Temurin JDK21 build (no surprise)
    • Docker is absent
    • updatecli and goreleaser compile without a problem
    • 1.5 years ago, Bruno wrote a blog post about Jenkins and RISC-V
      • Two conditions were to be met until the Jenkins project considers adding this platform:
        • Temurin is officially available for RISC-V, meaning we’ll be able to download a binary package for RISC-V from the official AdoptOpenJDK website.
        • Docker is officially available and supported for RISC-V, which means we’ll be able to download a binary package for RISC-V from the official Docker website.
        • 1302×745 60.3 KB
        • Depending on the Linux distro, you can have today:
          • A working Docker ecosystem
          • To rebuild Docker without too much hassle
          • Or be left without a solution (Hello Fedora 38)
  • Damien shows us how to release a new agent version