Jenkins 2.7.4 fails to load some plugins

[zhu kane]

I'm using official docker image(2.7.4) to launch Jenkins CI. The Jenkins data locates in external disk and is mounted by container. I use Jenkins in this way for more than a year. The original version was 1.6.x LTS, I always upgrade Jenkins to new LTS version bi-weekly or monthly. But after restarting the container today, Jenkins informs me that some job config data is unreadable. The error message looks like below,

CannotResolveClassException: hudson.plugins.git.GitSCM, CannotResolveClassException: com.cloudbees.jenkins.plugins.BitBucketTrigger, CannotResolveClassException: hudson.plugins.emailext.ExtendedEmailPublisher, CannotResolveClassException: hudson.plugins.parameterizedtrigger.BuildTrigger

However the git plugin(2.0.0) already is listed as installed. There was no luck after I manually downgraded it to 1.21.0. I also checked the jar file <jenkins_home>/plugins/git/WEB-INF/lib/git.jar, it's a valid jar file. And the GitSCM.class can be found inside it. I'm wondering why those classes can not be resolved.

This error definitely breaks CI/CD of my project. The git and triggering downstream totally does not work now.

Is there any way to fix it?

Thanks.

Kane

https://vme360.com

[zhu kane]

I worked it out! 

The system log of Jenkins showed me the hints. The problematic git client plugin and parameter plugin were not loaded due to missing dependencies plugins, such as git plugin and build step plugin. Reinstalling the missing plugins fixed the problem.

It's really strange why the git plugin and so on became uninstalled. I recall some plugins failed to be upgraded due to network issue. Anyway the partial upgrading of plugins should not break the plugin loading.

Kane

https://vme360.com

[Daniel Beck]

> On 01.10.2016, at 08:22, zhu kane <kan...@gmail.com> wrote:
>
> Anyway the partial upgrading of plugins should not break the plugin loading.

Tracked as JENKINS-14616

[zhu kane]

Daniel, thanks for your information.

I had a look at the issue 14616, looks like the major issue of it had been fixed for a while. Only two edge cases are still opening. I did upgrade the existing plugins via the official Jenkins update site, not manually updating them. Not sure if they are the same problem.

Kane

https://vme360.com

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/EB0414C8-B534-4DDE-8C3F-55A4F1B737CF%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.