Open timja opened 11 years ago
veen:
Slightly different workaround for our installation:
# no .pinned file exists, only .disabled mv $JENKINS_HOME/plugins/maven-plugin.jpi.disabled $JENKINS_HOME/plugins/maven-plugin.jpi.pinned # restart jenkins /etc/init.d/jenkins restart
This struck quite recently for some reason
Has this been resolved by extraction of Maven Project from core?
maven-project has long been a plugin, so no. It was moved out of the core source repository.
[Originally duplicated by: JENKINS-19930]
Start 1.490 on a clean home dir, then ask to upgrade the Maven plugin to version 1.491, and restart. After the restart, there are linkage errors from the Maven plugin, predictably enough (since it is using 1.491+ core APIs); but all of Jenkins fails to start, making it impossible to use the GUI to back out the update. (Workaround: delete $JENKINS_HOME/plugins/maven-plugin.jpi.pinned.)
followed by various errors from hudson.ExtensionFinder$Sezpoz.scout and similar; and then
followed by Jenkins shutting down (and throwing some more errors).
If a plugin fails to start due to linkage errors, it should be disabled, but that should prevent the whole application from starting.
Originally reported by jglick, imported from: Jenkins fails to start after error in hudson.maven.PluginImpl.init