-
Bug
-
Resolution: Unresolved
-
Major
-
- Latest LTS Jenkins (version 2.426.2) and latest available Jenkins (version 2.440).
- OpenJDK 11.
- AmazonLinux 2 up to date.
- Jenkins is installed using RPM packages.
- Jenkins is deployed in latest Apache Tomcat 9 (version 9.0.84).
- Tested on latest stable Mozilla Firefox (version 121.0.1, 64-bit) and also in latest stable Google Chrome (version 120.0.6099.199, 64 bit).
- Plugins: see attached plain text file "jenkins-plugins.txt".- Latest LTS Jenkins (version 2.426.2) and latest available Jenkins (version 2.440). - OpenJDK 11. - AmazonLinux 2 up to date. - Jenkins is installed using RPM packages. - Jenkins is deployed in latest Apache Tomcat 9 (version 9.0.84). - Tested on latest stable Mozilla Firefox (version 121.0.1, 64-bit) and also in latest stable Google Chrome (version 120.0.6099.199, 64 bit). - Plugins: see attached plain text file "jenkins-plugins.txt".
We have successfully updated one Jenkins instance from 2.387.2 to 2.246.2, and then we have updated all the plugins. Right after that, if you try to use the JCasC import and export buttons, you will get an angry Jenkins icon and a java.lang.StackOverflowError stack trace in the log file catalina.out (see attached file). We have reproduced it if updating to Jenkins 2.440. It looks like a plugin issue.
After long hours of testing and incremental plugin updates depending on the number of dependencies, we have been able to reproduce the issue three times: updating the BlazeMeter plugin from 4.17 to 4.20 breaks JCasC.
