Jenkins : Known Java 11 Compatibility issues

This pages summarizes the status of the Jenkins ecosystem to run on Java 11.

How to contribute to this page

Given Jenkins has 1500+ plugins, this page is not meant to describe or link the status of every single component or plugins. Hence if you know the status of some component or plugin, feel free to add more information in the necessary places below.

• Ideally, if there is an associated JIRA issue, just add the java11-compatibility label on the issue, and it will then automatically show up below.
• If not, just add the information in the dedicated part.

Please note that this page is dedicated to the user-facing issues which impact the behavior. It is recommended to not set the labels for gradual code improvements and for minor issues like IllegalReflectiveAccess warnings in the system logs.

Links

• Associated "Java 11 support in Jenkins" Jenkins Enhancement Proposal 211 (JEP) 
• Java requirements in Jenkins
• Java 11 Developer Guidelines
• Java 11 Preview Availability Announcement
• JAXB usage in Jenkins plugins

Known compatibility issues

JIRA

(In case the list does not populate below, you can refer to the JIRA issues directly)

T	Key	Component(s)	Summary	P	Status	released as
	JENKINS-66251	jobconfighistory-plugin	After Jenkins upgrade Declarative Pipelines stopped working due to JobConfigHistory plugin		Open
	JENKINS-66029	implied-labels-plugin	Java 11 illegal access exception with implied labels plugin		Open
	JENKINS-65582	core	"WARNING: An illegal reflective access operation has occurred" on Unix with openJDK11		Open
	JENKINS-64831	remoting	illegal reflective access in remoting		Open
	JENKINS-64648	core	Illegal reflective access by jenkins.ClassLoaderReflectionToolkit in 2.275		Resolved	2.276
	JENKINS-64456	core, ldap-plugin	"Added a missed class for missing class telemetry. Class: com.sun.jndi.ldap.obj.MarshalledToObject" on AdoptOpenJDK11		Open
	JENKINS-64455	core, ldap-plugin	"Added a missed class for missing class telemetry. Class: com.sun.jndi.ldap.obj.AttrsToCorba" on AdoptOpenJDK11		Open
	JENKINS-64159	atlassian-bitbucket-server-integration-plugin	Intermittent failed to post build status due hostname not verified		Closed
	JENKINS-63808	cppcheck-plugin	cppcheck is not compatible with Java 11		Open
	JENKINS-63766	configuration-as-code-plugin, core, prometheus-plugin, workflow-cps-plugin	Jenkins Pipelines Memory Leak		Open
	JENKINS-62417	hp-application-automation-tools-plugin	Run Performance Test on Jenkins (Java version 11) error		Open
	JENKINS-62170	checkmarx-plugin	Checkmarx v8.90.4 plugin not compatible with JDK11		Closed
	JENKINS-62086	checkmarx-plugin	Getting java.lang.ClassNotFoundException exception javax.xml.bind.JAXBException checkmarx plaugin with agent using open jdk 11		Closed
	JENKINS-61920	core	java.lang.ClassNotFoundException: javax.annotation.CheckForNull		Resolved	Jenkins 2.237
	JENKINS-61521	core	"Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11		Resolved	jenkins-2.227
	JENKINS-61391	rich-text-publisher-plugin	Incompatible with java 11		Closed
	JENKINS-61212	cli	CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11		Open
	JENKINS-61176	_unsorted	Logstash-gelf is not supported in Java 11		Closed
	JENKINS-60725	core	"Added a missed class for missing class telemetry" on AdoptOpenJDK 11		Resolved	2,217
	JENKINS-60678	core	ComputerLauncher: Detection of AdoptOpenJDK 11 fails		Resolved	Jenkins 2.217
Authenticate to retrieve your issues

Showing 20 out of 68 issues

Various sources

JIRA issues are generally recommended for better tracking and ability to link between related tickets, but if there is not, you can still it below if a more free-form format:

• Replace me

JIRA Triage by the Java 11 Support Team

Warning: this is a work-in-progress, please reach out to the team if you want any confirmation.

JIRA Filter used to triage new/existing issues: https://issues.jenkins-ci.org/issues/?filter=19376

TL;DR: if you want to draw attention, making sure the java11 && scrub labels are set.

(java11 should generally be enough, but adding scrub will show even already Resolved issues. This could be useful for instance to draw attention on an already closed/resoved issue that you are not sure you should Reopen)