Attending:
Agenda:
- Container image updates for the Jenkins controller
- Container image updates for Jenkins agents
- Only one new release for the ssh agent (5.38.0)
- Bump Alpine Linux Version to 3.20.0
- Three new releases for docker-agent (3248.v65ecb_254c298-3, 3248.v65ecb_254c298-4 and 3248.v65ecb_254c298-5)
- Bump Git version on Windows to 2.45.2.windows.1
- hotfix(Windows Server Core LTSC2019) pin 2019 images to April version (#816) @dduportal
- Factorize jdk in docker-bake.hcl
- Bump Alpine Linux Version to 3.20.0
- Only one new release for the ssh agent (5.38.0)
- Docker-based quickstart tutorials
- 13.6K total downloads.
- Back to working on the main Jenkins installation thanks to docker.
- Work in progress on images:
- Controller:
- None.
- Docker-agent:
- Bump preview (EA) JDK21 version to 21.0.4+5
- Arm32 builds aren’t available
- Arm64 builds for Windows are now regularly available, but…
- “Yep we’ve been building them as evaluation pipelines for a while but they’re not yet ready to be a GA release.”
- Support for aarch64 Windows platform · Issue #616 · adoptium/adoptium-support · GitHub is where most of the information on that platform is.
- Docker-ssh-agent:
- Controller:
- Hardware in the loop community
- GitHub - openhil/openhil.github.io: Homepage for the Open Hardware in the Loop Community
- We are a forum for software engineers, hardware hackers, QA teams, and embedded board manufacturers to come together and have conversations about Hardware in the Loop (HiL or HitL) systems.
- We welcome folks to present their systems in the forum, ask questions about HiL CI/CD pipelines, and document our knowledge to help everyone along the path to build an effective system.
- 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 June 18, 2024 (see dev list)
- Jetty 12 + EE 8 in Jenkins weekly June 26 or July 3
- Jetty 12 + EE 9 + Spring Security 6.x in Jenkins weekly - TBD
- Platform SIG members can help
- Identify tasks for the “Require Java 17” step coming June 18
- Test drive the Jetty 12 + EE 9 prototype from the jakarta branch
- Built by the ci.jenkins.io job
- Rebuilds frequently as Basil finds new issues
- java -jar testing-jar is more than enough to test
- Running for the last 10+ days in Mark’s test environment
- Places that tend to have problems are forms presented to the user that do not retain the values entered by the users
- Watch for stack traces in the Jenkins console logs in case those might point to something interesting
- Built by the ci.jenkins.io job
- We could create a dockerfile or a docker image for people to test
- For the container, we could start with Artifacts of jakarta #72 : /org/jenkins-ci/main/jenkins-war [Jenkins]
- We could create a container based on this war and quickstart repo
- Start with the weekly release docker image, and then replace the war
- If you’re interested in testing, please send an email to Mark Waite
- Key milestones in the Spring Security 6.x upgrade
- Java 21 support - 2+2+2 Java Support Plan
- Jenkins enhancement proposal by Mark Waite submitted and being reviewed
- Needs more details before it is merged
- Mark needs to do more research
- Will transition to Java 17 on June 18 for the weekly, less than one month from now
- Need a list of tasks to do before that change happens
- Spring security 6.x requires Jetty 11 with Jakarta EE 9 (jakarta.servlet), not Jetty 10 with Jakarta EE 8 (javax.servlet)
- August 31, 2024 date seems likely to stick
- The last public build of Spring Framework 5.3.x is August 21, 2024
- Spring framework 6.1 and later require Java 17
- Special thanks to Basil Crow and Adrien Lecharpentier for their involvement.
- They’re working on the first steps to get this done (FileUpload, then JDK 17, and then 1 to 2 weeks later Jetty 10 with EE8 to Jetty 12 with EE9).
- Alternatives:
- Accept that if there is a security vulnerability reported in Spring Security 5.8.x between August 2024 and the end of October 2024, we may need to fork Spring Security and fix it ourselves
- Mark to start discussions in the mailing list to find alternatives
- We’ll choose the next LTS baseline Jun 26, 2024. The baseline release for the next LTS will be something prior to the requirement of JDK17.
- 12 weeks from June 26 (18th September 2024), we’ll choose an LTS baseline that requires Java 17. Most of the work prior to the switch to Spring 6.x should be ready by then.
- 4 tasks in Jira that could be done by anyone that could help us with the June 18th and 25th.
- Jenkins enhancement proposal by Mark Waite submitted and being reviewed