|
||||||||
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 |
[JIRA] (JENKINS-15702) InstantiationError: hudson.scm.AbstractCvs
michael.m.cla...@gmail.com (JIRA) Fri, 16 Nov 2012 05:02:47 -0800
- [JIRA] (JENKINS-15702) InstantiationE... dave.ehrenber...@solipsys.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... dave.ehrenber...@solipsys.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... dave.ehrenber...@solipsys.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... ho...@farzad.net (JIRA)
- [JIRA] (JENKINS-15702) Instantia... ho...@farzad.net (JIRA)
- [JIRA] (JENKINS-15702) Instantia... michael.m.cla...@gmail.com (JIRA)
- [JIRA] (JENKINS-15702) Instantia... ho...@farzad.net (JIRA)
- [JIRA] (JENKINS-15702) Instantia... suresh.avadh...@gmail.com (JIRA)
The exception is being thrown whilst trying to load an historic build record given the stack trace at the top of this issue. If this was caused by the initialising of the plugin then I'd expect more people to have had this problem. Do you only get the exception when you try and access a previous run of a job and, if so, does this only affect job histories for jobs that were run before the last server restart, and not those run since then?