Checking the release notes at
https://www.oracle.com/java/technologies/javase/11-0-17-relnotes.html
I see 11.0.17 contains fixes for JDK-8231454 and JDK-8268773, which
are relevant to Jenkins. The update of tzdata will also resolve
JENKINS-69635. The fix for JDK-8231454 was already worked around in
Pipeline: Groovy and Script Security, and I manually stepped through
the workaround code on 11.0.17 to verify that it was harmless (though
unnecessary) on an 11.0.17 JVM with the fix for JDK-8231454. The fix
for JDK-8268773 should not be needed as of recent versions of
Remoting. I ran my local development Jenkins controller on 11.0.17 and
did not experience any problems running various job types
interactively. I also ran the following test suites on 11.0.17
successfully:

- Jenkins core smoke tests
- Pipeline: Groovy
- Script Security
- Remoting

A quick perusal of
https://mail.openjdk.org/pipermail/jdk-updates-dev/2022-October/ does
not appear to show any major regressions in the past week since the
release took place, unlike 11.0.16 (where
https://mail.openjdk.org/pipermail/jdk-updates-dev/2022-August/016460.html
was being actively discussed).

Based on the above, I do not anticipate any problems with the C2 JIT
compiler, the metaspace, or container awareness for cgroups v2 (which
are the three categories where we experienced issues with 11.0.16). If
it is feasible without too much effort to run the BOM test suite
against 11.0.17 before our agents are upgraded, I think that would be
safest. But if that is not practical, I think it would be fine to
upgrade our agents and merely monitor core and BOM builds afterward to
ensure no new failures are introduced.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjrwu98N7DwTgH84eeJqpKcdM7Z7Mk9c2HY7zUn-y8%3DDmQ%40mail.gmail.com.

Reply via email to