JUG Lausanne: Leap from Java 8 to Java 11 in Jenkins. Our war story
Aujourd'hui, 14 nov. à 18:30
On Nov 14 JUG Lausanne organizes a meetup about support of Java 11 in Jenkins. Oleg Nenashev will be presenting there. Although the topic is largely about Java support side, it may be interesting to Jenkins administrators and developers who are interested in adopting Java 11. Please register here:
https://www.meetup.com/JUGL-the-Java-User-Group-of-Lausanne/events/255766372/ Jenkins, one of the leading open-source automation servers, still requires Java 8 even though Java 9 and above have been officially released. Over the last year Jenkins contributors were working towards the support of Java 11 (Jenkins JEP-211). Jenkins has a huge and sometimes legacy Java/Groovy/native codebase, includes DSL engines, and depends on many upstream libraries and modules (including ones deleted from Java 11). There are also hundreds of independently-released plugins which we want to keep compatible. It was a thorny way, but Java 11 support is almost ready to be released. In this talk I would like to share our experiences and talk about potential obstacles others may hit while implementing Java 11 support in their projects. What issues have we hit while implementing support of Java 11 in the core? Are modules and deprecations that tricky for a web application (spoiler: no)? How have we enabled building and testing with OpenJDK 11 in our Maven-based pipelines? And how have we retained Java 8 compatibility after all these changes? Registration:
Nous avons temporairement désactivé la possibilité de naviguer vers les tags.