[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Marek Parfianowicz resolved as Fixed Jenkins / JENKINS-34439 Clover plugin still has problems with pipeline builds Change By: Marek Parfianowicz Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Marek Parfianowicz commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds Fix will be delivered in 4.8.1+ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Marek Parfianowicz started work on JENKINS-34439 Change By: Marek Parfianowicz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Matias Montes commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds I can confirm that in 4.7.1 still there is no coverage graph in the main Status page for the job. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Marek Parfianowicz commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds Can you confirm that this still happens in the latest Jenkins Clover Plugin - version 4.7.1? I'm asking because in this version I fixed NPE and closed two other tickets: JENKINS-38956 and JENKINS-39410 which look very similar to yours. I suspect that this bug report can be closed too. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title suresh nallamilli updated an issue Jenkins / JENKINS-34439 Clover plugin still has problems with pipeline builds Change By: suresh nallamilli Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Ahmed Musallam commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds Andor Dávid Mark Cariddi We have seen this issue on my project. It turned out to be a missing config for the clover publisher. Specifically the config. This config's absence is not handled properly in the plugin, I opened an issue here: https://issues.jenkins-ci.org/browse/JENKINS-40297 target/site/clover clover.xml 70 80 80 40 40 40 0 0 0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Mark Cariddi commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds I am still seeing this issue with the 4.6.0 plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title
Andor Dávid edited a comment on JENKINS-34439
Re: Clover plugin still has problems with pipeline builds
Same problem here{code}step([ $class: 'CloverPublisher', cloverReportDir: 'tests/_output/coverage', cloverReportFileName: 'coverage.xml']){code}{code}[Pipeline] stepPublishing Clover coverage report...Publishing Clover HTML report...Publishing Clover XML report...Publishing Clover coverage results...[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // wrap[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.lang.NullPointerException at hudson.plugins.clover.CloverPublisher.processCloverXml(CloverPublisher.java:250) at hudson.plugins.clover.CloverPublisher.performImpl(CloverPublisher.java:202) at hudson.plugins.clover.CloverPublisher.perform(CloverPublisher.java:167) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:59) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Finished: FAILURE{code} The error above comes with Jenkins v2.25Clover plugin v4.7.0Downgrade the Clover plugin to v4.6.0 solves the problem
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Andor Dávid commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds Same problem here step([ $class: 'CloverPublisher', cloverReportDir: 'tests/_output/coverage', cloverReportFileName: 'coverage.xml' ]) [Pipeline] step Publishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... Publishing Clover coverage results... [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // wrap [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline java.lang.NullPointerException at hudson.plugins.clover.CloverPublisher.processCloverXml(CloverPublisher.java:250) at hudson.plugins.clover.CloverPublisher.performImpl(CloverPublisher.java:202) at hudson.plugins.clover.CloverPublisher.perform(CloverPublisher.java:167) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:59) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Finished: FAILURE Add Comment
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title
Michael Rose edited a comment on JENKINS-34439
Re: Clover plugin still has problems with pipeline builds
I am seeing similar behaviour. The following error is in the console output: Originally I was seeing errors like this. When this was happening I would be able to access the Clover Summary Report but the Clover HTML Report was an empty page. {quote}IOException when checking workspace path:remote file operation failed: /JENKINS/WORKSPACE/PATH/FOR/PROJECT at hudson.remoting.Channel@7e2840c5:HOSTNAME: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@1359cfca{quote} Now, I am getting this error in the console output:{quote}java.lang.NullPointerException at hudson.FilePath.isAbsolute(FilePath.java:271) at hudson.FilePath.resolvePathIfRelative(FilePath.java:256) at hudson.FilePath.(FilePath.java:252) at hudson.FilePath.child(FilePath.java:1267) at hudson.plugins.clover.CloverPublisher.performImpl(CloverPublisher.java:161) at hudson.plugins.clover.CloverPublisher.perform(CloverPublisher.java:152) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:68) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:59) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745){quote}And the Clover Summary report in all builds now navigate to the oops page.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Michael Rose commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds I am seeing similar behaviour. The following error is in the console output: IOException when checking workspace path:remote file operation failed: /JENKINS/WORKSPACE/PATH/FOR/PROJECT at hudson.remoting.Channel@7e2840c5:HOSTNAME: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@1359cfca Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title stephenconnolly assigned an issue to Unassigned Jenkins / JENKINS-34439 Clover plugin still has problems with pipeline builds Change By: stephenconnolly Assignee: stephenconnolly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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/d/optout.
[JIRA] (JENKINS-34439) Clover plugin still has problems with pipeline builds
Title: Message Title Neil Jarrett commented on JENKINS-34439 Re: Clover plugin still has problems with pipeline builds I am also seeing that after a period of time (not sure how long) the stats disappear. On a build page it is showing: Clover Code Coverage - null% method null, conditional null, statement null. Also, clicking on the Clover Summary Report gives the following stack trace error: com.google.common.util.concurrent.UncheckedExecutionException: java.lang.NullPointerException at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2234) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache.getOrLoad(LocalCache.java:3969) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4829) at hudson.plugins.clover.CloverBuildAction.getResult(CloverBuildAction.java:162) at hudson.plugins.clover.CloverBuildAction.getTarget(CloverBuildAction.java:111) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:674) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at
