|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
One thing we need to look at is if the plugin in question (analysis-core in most cases but in some other cases warning plugin) had successfully loaded.
One plugin failing to start does not block Jenkins from starting up; it just leaves the failed plugin as-is and tries to load the rest, and when that happens, people would see errors like this.
What we really need is the compete log output from Jenkins from the begenning, not just the NoClassDefFoundError portion. For example, the currently attached log file indicates that it didn't even try to load the anaylsis-core plugin, which suggests the plugin just wasn't present.
If you are seeing this error, please attach the whole log so that we can get to the bottom of it. Thank you!