-
Bug
-
Resolution: Unresolved
-
Critical
-
None
Jenkins is not starting up during the course of upgrade from version 2.471 to 2.489 due to failure of initialization of Scriptler plugin. Scriptler was upgraded from : 363.vd97ef616cb_f9 to 392.va_dce718b_3e40.
Below are the steps which was observed during the crash of the Jenkins.
- INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins
- INFO o.j.p.s.ScriptlerLoadingTasks#synchronizeConfig: initialize Scriptler
- INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins
- SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed ScriptlerLoadingTasks.synchronizeConfig
- SEVERE hudson.util.BootFailure#publish: Failed to initialize Jenkins
- INFO hudson.lifecycle.Lifecycle#onStatusUpdate: Stopping Jenkins
We disabled the Scriptler plugin by creating a file named scriptler.jpi.disabled under location: mnt/jenkins_home/plugins and pinned Scriptler to previous stable version of 363.vd97ef616cb_f9.
After disabling, Jenkins was able to start.
[JENKINS-75097] Failed ScriptlerLoadingTasks creating issue in Jenkins Startup
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "PR-139 revert breaking change in scriptler plugin (Web Link)" [ 30486 ] |
Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
This may be a duplicate of
JENKINS-75019. Does it also work with scriptler plugin 376.v152edd95b_ca_f?Can you provide detailed steps so that others can duplicate the failure on a fresh installation of Jenkins?