(Logs in the attachment)
I had a Jenkins mastered configured with Jenkins Configuration as Code plugin.
Jenkins version: 2.138.?
JCasC version: 1.3
and number of plugins requiring upgrade
I've updated JCasC to 1.5, Jenkins to latest lts (2.150.?) in a basic docker image, and in the file with plugins all the version numbers got replaced with "latest"
I tried to rebuild image and start a container using docker compose
It started well, but when configuring Active Directory it failed:
(line 1023) SEVERE: Failed ConfigurationAsCode.init
but instead of simply failing it restarted Jenkins:
(line 1131) jenkins_1 | INFO: Jenkins stopped
(line 1132) jenkins_1 | Feb 20, 2019 12:15:24 PM jenkins.model.Jenkins$22 run
(line 1133) jenkins_1 | INFO: Restarting VM as requested by SYSTEM
when the restart was happening I updated configuration file and removed the Active Directory section so there was no exceptions next time but the restart happened again
(starting from line 2380)
jenkins_1 | Feb 20, 2019 12:22:06 PM hudson.WebAppMain$3 run
jenkins_1 | INFO: Jenkins is fully up and running
jenkins_1 | Feb 20, 2019 12:22:08 PM jenkins.model.Jenkins$22 run
jenkins_1 | INFO: Restarting VM as requested by SYSTEM
jenkins_1 | Feb 20, 2019 12:22:08 PM jenkins.model.Jenkins cleanUp
jenkins_1 | INFO: Stopping Jenkins
jenkins_1 | Feb 20, 2019 12:22:08 PM jenkins.model.Jenkins$18 onAttained
jenkins_1 | INFO: Started termination
[...]
And it keeps restarting.
I've seen same issue before when updating plugins when JCasC was used - both via UI or plugins.txt, but not EVERY time
this is a serious instability issue with JCasC
anyone experienced something like that?
HELP!
BR
Ewelina