Status: Closed (View Workflow)
Resolution: Cannot Reproduce
Main server: Linux VM (CentOS 7.5)
Nodes: 3 Linux VM (CentOS 7.8), 3 Windows Server 2016
Plugin: JobConfigHistory 2.28.1 (problem also was replicated with v2.24)
Browsers: Chrome (v92), Firefox (v90) and Safari (v14)
We recently upgraded our Jenkins instance from 2.204.4 to version 2.297.
We also upgraded Java from version 8 to 11 (openJDK).
All plugins were upgraded. (See attached list of installed plugins)
We've been reported that Declarative pipelines can't be created due to an error (see attached). Existing pipeline jobs are working fine after the upgrade, this problem is only affecting new jobs. If we copy an existing pipeline job, the resulting job is also working fine. Just the ones that are created from scratch are not working.
We tried the below without success:
Downgrade the JobConfigHistory plugin to 2.24
Go back to use Java 8 in the main server and all the nodes.
This issue only affects to declarative pipelines, scripted ones are working fine.
We've disabled the plugin and the issue is gone. Our Jenkins instance is not reachable externally.
hugo9995 that version of OpenJDK 11 is the original JDK 11 release from almost 3 years ago. There have been 12 patch releases since then. You need to upgrade to the current patch release. It is available from Adoptium, from Red Hat, from Amazon (Corretto), and from others.
Hi, I've updated the Java version to use the latest corretto in all main server and nodes.
jshell --add-modules java.xml | Welcome to JShell -- Version 11.0.12 | For an introduction type: /help intro jshell> import javax.xml.transform.TransformerFactory; jshell> var tf = TransformerFactory.newInstance(); tf ==> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl@5f341870 jshell>
java -version openjdk version "11.0.12" 2021-07-20 LTS OpenJDK Runtime Environment Corretto-184.108.40.206.1 (build 11.0.12+7-LTS) OpenJDK 64-Bit Server VM Corretto-220.127.116.11.1 (build 11.0.12+7-LTS, mixed mode)
hugo9995 Does this issue persist or can this bug be closed? If I do not hear back within the next week or so, I will assume this bug can be closed.