Cobertura plugin

Hi Ross,

Thanks for the submission! That's awesome!

There are some guys here who were looking for this.

Cheers,
Edwin

No worries, glad that it's useful I can't take too much credit for it, as much of the code was 'inspired' by the Clover plugin! I'm currently working on a plugin for PMD, and if I have time, I'll try to look at doing something with Nant and Nunit integration.

Hi all, just letting you know that I've just put up version 0.9.1 of the Cobertura plugin. This release includes the ability to specify whether you want notifications sent if the Cobertura line rate exceeds a specific threshold. I'm going to start working on CBRT-1, which is the issue surrounding identifying classes with the most significant coverage changes now, feel free to let me know if there's any other bits of functionality that you'd like to see.

Hi again, I've put up version 0.9.2 which now includes showing the significant coverage changes since the last build (ie. increases/decreases in coverage). I still need to do a little bit of work in sorting the list, and perhaps having separate sections for increases/decreases. Let me know what you think

I'm having some issues getting it set up in my plan.
My ant script uses the cobertura-report task to create an xml report in the dist\reports\coverage\xml directory called coverage.xml

<cobertura-report format="xml" destdir="dist/reports/coverage/xml" srcdir="src/java"/>

Now in the setup for my build plan, what do I have to set the "Cobertura XML Directory" to?
I've tried:

• **/dist/reports/coverage/xml/*.xml
• **/dist/reports/coverage/xml/coverage.xml
• **/dist/reports/coverage/xml
• dist/reports/coverage/xml/coverage.xml

All with no luck. When the build runs, it has the "% Line Rate" and the "% Branch Rate" both as 0% (even though my coverage.xml has non-zero values for those)
Am I missing something simple here?

I've even tried using the test-cobertura-report.xml that is used as part of the plugin tests (I just checked it into my repository and pointed my "Cobertura XML Directory" directly to it).

I'm using 0.9.3 of the plugin on bamboo 1.1 (had the same problem in 1.0.5) and cobertura 1.8.

Thanks.

Hi James, thanks for letting me know. It sounds like the build processor can't find the coverage XML file. I've just put up version 0.9.4 which includes a little bit more logging. Would you be able to check the bamboo.log file to see if lines similar to the following are appearing?

2007-05-09 06:51:51,038 INFO [BAM:Default Queue:BuildExe] [CoberturaBuildProcessor] Running Cobertura Build Processor over source dir:/Users/ross/bamboo-home/xml-data/build-dir/BLAH-DEF path pattern:**/report/cobertura-xml/coverage_no_dtd.xml
2007-05-09 06:51:53,066 INFO [BAM:Default Queue:BuildExe] [CoberturaBuildProcessor] Parsing file: /Users/ross/bamboo-home/xml-data/build-dir/BLAH-DEF/report/cobertura-xml/coverage_no_dtd.xml

If you don't see a 'Parsing File' log entry, then the build processor wasn't able to locate the coverage XML file. I was also running into problems because we are running our builds offline, and the XML parser is attempting to validate the Cobertura DTD, so I had to remove the DTD from the Coverage XML file in our Ant task.

Let me know how it goes, feel free to send me an email at piaross at gmail dot com if it's still causing problems.

Cheers,

Ross

maybe I caught you mid-update, but the supplied jarfile 1.0.1 doesn't work with product 1.2 (if it is relevent, the plugin xml file inside the jar says 1.1 max)

I've got Bamboo 1.1.2 and cobertura_bamboo-1.0.1.jar. The former is installed in /opt/tomcat/webapps/bamboo (*.ftl, admin/, reports/, etc.), and works in
/opt/bamboo (bamboo.cfg.xml, bamboohome, database).

Based on the instructions above, I put the cobertura_bamboo-1.0.1.jar in /opt/tomcat/webapps/bamboo/WEB-INF/lib.

I restarted tomcat, but there's no sign of Cobertura in the builder configuration. Did I do something wrong, put the file in the wrong place? Did I miss another step? How can I diagnose the issue?

Hi Ross,

I try to cconfigure your plugin using Bamboo 1.2.3, Maven 2.0.7 as Builder and org.codehaus.mojo:cobertura-maven-plugin:2.0 for Cobertura engine.
For information org.codehaus.mojo:cobertura-maven-plugin:2.1 with Cobertura 1.8 engine fail with Maven2.
org.codehaus.mojo:cobertura-maven-plugin:2.0 provides Cobertura 1.7 and seems to be OK.

Then, with your plugin (1.0.3) I am not able to see the Notification configuration panel, neither the Code Coverage build results (screenshots 10 and 11). Ony raw data are available in the Metadata panel.

Any idea.

Hi all,

First of all, this really look nice! 

However

I'm trying to use this plugin using Bamboo version 2.0.6 build 808. I have the latest 2.1.2 cobertura plugin. I'm using maven 2.0.7 and jdk 1.6. And I'm using 2.2 of the maven-cobertura plugin specifying xml as a report (Just to make a complete list)

 The problem that I see in the Bamboo logs is that the NumberUtils class seems to have changed in this bamboo version, or?

 Any help is much appriciated and nice work!

/Christian

java.lang.NoSuchMethodError: com.atlassian.bamboo.util.NumberUtils.padWithZeroes(Ljava/lang/Number;I)Ljava/lang/String;
at com.atlassian.bamboo.plugins.cobertura.CoberturaPostBuildIndexWriter.updateIndexDocument(CoberturaPostBuildIndexWriter.java:41)
at com.atlassian.bamboo.index.BuildResultsSummaryDocumentFactory.getDocument(BuildResultsSummaryDocumentFactory.java:141)
at com.atlassian.bamboo.index.DefaultBuildResultsIndexer.indexBuildResult(DefaultBuildResultsIndexer.java:132)
at com.atlassian.bamboo.build.pipeline.tasks.SaveBuildTask.call(SaveBuildTask.java:69)
at sun.reflect.GeneratedMethodAccessor396.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at org.springframework.orm.hibernate.HibernateInterceptor.invoke(HibernateInterceptor.java:117)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.orm.hibernate.HibernateInterceptor.invoke(HibernateInterceptor.java:117)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy49.call(Unknown Source)
at com.atlassian.bamboo.v2.build.agent.LocalBuildResultProcessor.processBuildResult(LocalBuildResultProcessor.java:99)
at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:111)
at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:101)
at com.atlassian.bamboo.build.pipeline.concurrent.NamedThreadFactory$1.run(NamedThreadFactory.java:32)
at edu.emory.mathcs.backport.java.util.concurrent.helpers.ThreadHelpers$1.run(ThreadHelpers.java:34)
at java.lang.Thread.run(Thread.java:619)
 

Great plugin, however I have some odd results using the plugin. On the detailed build tab (of a specific build) I get this for line rate:
9.223372036854776E29% (0%)
and this for branch rate
922337203685477600000000000000000000000000000% 
 
I'm using the XML report from cobertura, this xml report is generated upon a merged SER file (merged using the cobertura ant task).

Hi Ross

Cool plugin, but we noticed when using it that the averages for line rate and branch rate werent accurate when using more than two coverage reports. We made a patch for it using your latest code of trunk and now it gives accurate results.

Have a look.

Regards

Fuzail Sarang

Silvermoon Business Systems