I think the upgrade to Cobertura 1.4 helped, or at least the exception you noted earlier does not seem to be in the most recent log file.
I'm sorry that didn't enable your jobs for you. Since you mention that "smart Jenkins" is enabled, you might experiment with disabling the "Smart Jenkins" plugin, then restarting Jenkins. If that resolves the issue, then that may point to a problem with the "Smart Jenkins" plugin, or with your definition of the times when jobs are allowed to be run on Jenkins. Mark Waite >________________________________ > From: "sampath.rajago...@vce.com" <sampath.rajago...@vce.com> >To: jenkinsci-users@googlegroups.com >Sent: Monday, May 7, 2012 8:44 PM >Subject: RE: After disk upgrade, jenkins build stopped working > > >I managed to update Cobertura plugin to 1.4, though it was not visible in my >environment. >Somehow, the problem still persists. Upgrading to 1.4, did not help. Not sure >if anyone else is in a similar situation. >The logs are clean as much as it could be. No idea why the jobs go in a >“Blocked” state as observed in smart Jenkins. Here is the content of the log. > >Mark, I truly appreciate all the support you have been giving me. > >May 7, 2012 7:31:23 PM hudson.triggers.SCMTrigger$Runner run >INFO: SCM changes detected in Vol_Services. Job is already in the queue >May 7, 2012 7:22:40 PM hudson.WebAppMain$2 run >INFO: Jenkins is fully up and running >May 7, 2012 7:22:27 PM hudson.TcpSlaveAgentListener <init> >INFO: JNLP slave agent listener started on TCP port 42703 >May 7, 2012 7:22:27 PM jenkins.InitReactorRunner$1 onAttained >INFO: Completed initialization >May 7, 2012 7:22:27 PM jenkins.InitReactorRunner$1 onAttained >INFO: Loaded all jobs >May 7, 2012 7:22:23 PM jenkins.InitReactorRunner$1 onAttained >INFO: Augmented all extensions >May 7, 2012 7:22:23 PM jenkins.InitReactorRunner$1 onAttained >INFO: Started all plugins >May 7, 2012 7:22:23 PM jenkins.InitReactorRunner$1 onAttained >INFO: Prepared all plugins >May 7, 2012 7:22:23 PM jenkins.InitReactorRunner$1 onAttained >INFO: Listed all plugins >May 7, 2012 7:22:23 PM hudson.PluginManager$1$3$1 isDuplicate >INFO: Ignoring /var/lib/jenkins/plugins/cobertura.jpi because >/var/lib/jenkins/plugins/cobertura.hpi is already loaded >May 7, 2012 7:22:23 PM hudson.ClassicPluginStrategy createPluginWrapper >INFO: Plugin ldapemail.hpi is disabled >May 7, 2012 7:22:23 PM jenkins.InitReactorRunner$1 onAttained >INFO: Started initialization > > >From:jenkinsci-users@googlegroups.com >[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite >Sent: Monday, May 07, 2012 4:32 PM >To: jenkinsci-users@googlegroups.com >Subject: Re: After disk upgrade, jenkins build stopped working > >The Cobertura plugin version history >at https://wiki.jenkins-ci.org/display/JENKINS/Cobertura+Plugin#CoberturaPlugin-VersionHistory shows > that the change is included in the 1.4 release of the Cobertura plugin. That >version was released on 5 May 2012. It is visible in the Jenkins Update >Center on my installation of Jenkins, so I suspect it is available in yours as >well. > >Navigate to http://localhost:8080/pluginManager/ and review the available >plugin updates. Cobertura 1.4 should be in the list. > >I'm not aware of a way to request notification when a specific fix has been >released for a plugin or for core Jenkins. I like the idea, but I don't know >how that would be implemented between the Jira bug tracker and the process of >releasing plugin versions. > >Mark Waite > >> >>________________________________ >> >>From:"sampath.rajago...@vce.com" <sampath.rajago...@vce.com> >>To: jenkinsci-users@googlegroups.com >>Sent: Monday, May 7, 2012 2:44 PM >>Subject: RE: After disk upgrade, jenkins build stopped working >> >>Referring to https://issues.jenkins-ci.org/browse/JENKINS-11398, I see the >>updates posted by Seiji Sogabe (user name:dogfood) and >>"plugins_cobertura#70" is part of 1.463-SNAPSHOT release >>(http://ci.jenkins-ci.org/job/plugins_cobertura/70/). >> >>I would like to know when this fix will be available from jenkins download >>center (http://updates.jenkins-ci.org/download) >>Essentially fix to >>src/main/java/hudson/plugins/cobertura/dashboard/CoverageTablePortlet.java >> >>I would like to be prompted for downloading a release containing this fix, to >>move ahead as the CI environment is not functional as of now. I would guess >>this will be available as part of 1.463 ? >> >>Please advise. thanks >> >> >>From:jenkinsci-users@googlegroups.com >>[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite >>Sent: Sunday, May 06, 2012 1:45 PM >>To: jenkinsci-users@googlegroups.com >>Subject: Re: After disk upgrade, jenkins build stopped working >> >>I would guess (looking at the classpath mentioned in the trace) that the >>cobertura plugin is the first plugin to attempt the steps. A google search >>hints that there may be a bug that was just recently fixed in the Cobertura >>and Emma plugins which has that stack trace. You might review >> >>https://issues.jenkins-ci.org/browse/JENKINS-11398 >> >>to see if it matches your situation. >> >>Mark Waite >> >>> >>>________________________________ >>> >>>From:"sampath.rajago...@vce.com" <sampath.rajago...@vce.com> >>>To: jenkinsci-users@googlegroups.com >>>Sent: Sunday, May 6, 2012 3:14 PM >>>Subject: RE: After disk upgrade, jenkins build stopped working >>> >>>Thanks Mark for that note. >>>Just curious – what are the plugins that correspond to the following >>>exceptions (as well as dependency plugins if any) – >>>Failed to load >>>hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl >>>java.lang.LinkageError: Failed to resolve class >>>hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl >>> >>>Caused by java.lang.TypeNotPresentException: Type >>>hudson.plugins.view.dashboard.DashboardPortlet not present >>>Caused by java.lang.ClassNotFoundException: >>>hudson.plugins.view.dashboard.DashboardPortlet >>> >>>In particular for dashboard.DashboardPortlet. >>> >>>Thanks >>> >>> >>>From:jenkinsci-users@googlegroups.com >>>[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite >>>Sent: Sunday, May 06, 2012 1:06 PM >>>To: jenkinsci-users@googlegroups.com >>>Subject: Re: After disk upgrade, jenkins build stopped working >>> >>>I doubt the addition of the disc space is the cause of the problem. >>> >>>Did the disc become full during previous operation? If so, then attempts to >>>write to the disc may have failed at that time. If the writes failed, then >>>it is possible that the plugin you're trying to reference is not completely >>>installed, or is installed and not completely configured. >>> >>>You might try attempting to reconfigure the plugin. If the issue is not >>>resolved after you reconfigure the plugin, you could try disabling the >>>plugin, restarting Jenkins, then enabling the plugin again. If disable and >>>enable does not repair it, then you could try removing the plugin >>>completely, restarting Jenkins and installing the plugin again. >>> >>>Mark Waite >>> >>>> >>>>________________________________ >>>> >>>>To:jenkinsci-users@googlegroups.com >>>>Sent: Sunday, May 6, 2012 2:51 PM >>>>Subject: After disk upgrade, jenkins build stopped working >>>> >>>>Not sure if any one else has run into this issue. After disk space >>>>addition, the builds stopped working. ‘build now’ link is not doing >>>>anything. >>>>Appreicate your input. Is there a best practice that one should be >>>>following while doing such a maintenance work ? >>>> >>>>The VM where Jenkins CI is running, was reaching to a point of disk space >>>>being full. Our Admin decided to increase the disk space. After that the >>>>builds stopped working. Both “Build Now” link as well as scheduled builds >>>>do not work anymore. Here is the exception details in the log – >>>> >>>>Failed to load >>>>hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl >>>>java.lang.LinkageError: Failed to resolve class >>>>hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl >>>> >>>>Caused by java.lang.TypeNotPresentException: Type >>>>hudson.plugins.view.dashboard.DashboardPortlet not present >>>>Caused by java.lang.ClassNotFoundException: >>>>hudson.plugins.view.dashboard.DashboardPortlet >>>> >>>>Looking at the link https://issues.jenkins-ci.org/browse/JENKINS-11398, I >>>>installed Dashboard plugin but it still does not help. The environment >>>>stopped working. >>>> >>>>When I go to “smart Jenkins” page, everything shows up in “Blocked” state. >>>> >>>>Never realized that adding extra disk space would lead to this situation. >>>> >>>>Thanks for any help >>>> >>> >> > >
