Update Jenkins to v2.555.3

[targos]

https://www.jenkins.io/doc/upgrade-guide/2.555/

Most notable change is that it now requires Java 21 for controllers and agents.
We have a lot of agents running on Java 17!

Procedure (as done on ci-release):

• Make sure all agents have Java 25 or 21
• Update plugins from the Jenkins UI and restart Jenkins
• Update system and Jenkins (apt upgrade)
• Update plugins again from the Jenkins UI and restart Jenkins
• Reboot the server

[richardlau]

Do we know if it includes the fix for the issue in #4247?

cc @sxa

[richardlau]

Most notable change is that it now requires Java 21 for controllers and agents. We have a lot of agents running on Java 17!

JVM versions are listed on https://ci.nodejs.org/computer/

[richardlau]

I think the post-17 Long Term Support versions of Java are 21 and 25, so where possible we should upgrade to 25 where available.

[sxa]

Yep that's correct - I've got a couple of jenkins agents running 25 so that should be the default choice now with 25 being LTS.
I'll see if I can confirm for sure but yes 2.555.x should include the fix. We'll need to decide if we want to re-enable the restart or not. As I mentioned somewhere else I'm not sure it's strictly required...

[sxa]

We still have Debian11/arm32 in the CI (e.g. test-azure-debian11-container-armv7l-1 which is used for the fanned arm32 jobs. Debian 11 does not have any JDK later than 17 in the repositories.

Options:

1. Remove Debian from the test matrix
2. Update those containers to a later Debian which has a jdk21 available (12 doesn't so it would have to be 13/trixie)
3. I do have what amounts to an "unofficial jdk25" build which was done using the Temurin build scripts and environment (Noting that temurin stopped producing arm32 builds after JDK17) which we could use for the Debian11 agents, although it wouldn't be automatically updated. That would be a path for allowing ust to continue with the systems we have.

[sxa]

jdk-21 is available for IBMi but according to @abmusse is not currently installed on our systems: https://www.ibm.com/support/pages/download-installation-and-usage-java-21-ibm-i-os

[sxa]

For SmartOS (the other potentially problematic platform) i'm not sure if they're in the default repositories but there are Illumos builds available on @ptribble's site at https://pkgs.tribblix.org/openjdk/#illumos-x86 so I would expect that to be feasible too and probably needs to be done as part of some of the other updates in #4259

[richardlau]

In terms of updating agents, I have been talking to @abmusse and @sxa and we'll handle updating Java on the IBM/RH platforms (AIX, IBM i, RHEL). And I have planned updates for the sharedlibs containers so might as well update Java when I do those. That is not an exhaustive list (and not a case of cookie-licking) but meant in the spirit of "if you're volunteering to help update the Java agents, perhaps start with something other than those" to avoid duplication.

[targos]

On https://ci-release.nodejs.org/computer/, we still need to update:

• rhel8/9_arm_cross_container-x64 (two hosts)
• aix72-ppc64_be (two hosts)
• win*-x64 (6 hosts) /cc @StefanStojanovic

[targos]

On https://ci.nodejs.org/computer/:

• smartos
• ibmi
• macOS
• freebsd decommissioned ansible: remove freebsd #4365
• debian12 ansible: update Java on Debian 12 machines #4367
• windows
• aix
• armv7 containers ansible: update Java for arm Dockerfiles #4358
• rhel and ubi8 containers
• ubuntu2404
• loong64