- 论坛徽章:
- 15
|
网上查到的:
It's a known bug (https://issues.jenkins-ci.org/browse/JENKINS-15892)
Copy/pasted for reference:
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.)
或者:
In my case it was because I had selected the git-client.jpi and git-server.jpi files for installation, but before they could be downloaded by Jenkins plugin manager, the download got stuck at a database plugin download. I restarted Jenkins and I think Jenkins mistook the not-yet-downloaded git plugin as already downloaded.
To solve the problem, just navigate to /var/lib/jenkins/plugins and delete the jpi files that are causing the problem. The restart Jenkins and your problem will be solved.
|
|