About the 2.545 weekly release with the broken packages: As discussed in Matrix (jenkinsci/release), Hervé Le Meur and I are currently pairing to issue a new set of fixed packages and we'll remove the Docker container tags with "jdk17" in it.
As pointed by Tim Jacomb, re-issuing packaging should be faster than triggering a new 2.546 (since the correct Docker containers with JDK21 do NOT need any changes). Le mercredi 7 janvier 2026 à 13:42:11 UTC+1, Damien Duportal a écrit : > I'm forking from > https://groups.google.com/g/jenkinsci-dev/c/SNsd_pLk4-k/m/jQDOF-3jCgAJ as > it is a distinct topic than the LTS backports for 2.541.1. > > Context: With https://github.com/jenkinsci/jenkins/pull/26018, we've > officially started to drop support of JDK17 (e.g. requiring JDK21) to run > Jenkins Core. > > It follows the "2+2+2" Java Support Plan described in > https://www.jenkins.io/blog/2023/11/06/introducing-2-2-2-java-support-plan/ > . > > This change has been released with 2.545: > https://www.jenkins.io/changelog/2.545/. > > But it had side effects: > > - There are Docker tags for the 2.545 with jdk17: it should not and > requires a fix. > - The packaging on some Linux platforms seems to have dependency > issues with JDK17/21/other JDK: > https://github.com/jenkinsci/packaging/issues/729 > > > I'm opening this email thread to have a centralized discussion and > tracking of fixes (so we won't do the same mistakes when we'll drop JDK21). > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/a618a336-a35e-40df-9d7d-d71c41cee4f3n%40googlegroups.com.
