Jenkins plugin merging
On Monday, 2 July 2012, Mikael Petterson wrote:
> Hi,
>
>
> Yes I guess this has been the situation for a while ;-)
>
> Yes we have a quite large coverage statistics file.
>
> When you say "capture" do you mean copy source files?
>
> Is the cobertura jenkins plugin merging coverage.xml files or is it the
> cobertura tool that does this?
>
> To me it also sounds like the cobertura tool is giving us this problem. I
> will have a look at it :-)
>
> I am really looking forward to your "coverage" plugin.
>
> Br,
>
> //mike
> -----Original Message-----
> From: jenkinsci-dev@googlegroups.com [mailto:
> jenkinsci-dev@googlegroups.com] On Behalf Of Stephen Connolly
> Sent: den 29 juni 2012 13:48
> To: jenkinsci-dev@googlegroups.com
> Subject: Re: Time consuming task in Cobertura plugin
>
> A long long time ago I identifies performance issues in the coverage
> plugins...
>
> Once the coverage.xml gets sufficiently large, you will hit the issue.
>
> Part of the problem is that we need to capture all the source code that
> has coverage results in order to be able to paint the source code.
>
> Another part of the problem is that we need to merge multiple coverage.xml
> files to produce an aggregate view of code coverage.
>
> These are "non-trivial" problems. In general you can work around by
> chucking more memory at the jvm that is doing the aggregation (i.e.
> the slave JVM) that will at least prevent the GC churn that slows things
> massively, however it is a work around as the core issue is the algorithm
> used to parse, merge and aggregate has some fundamental flaws.
>
> I have been threatening to rewrite them for some time....
>
> Still no sign of my mythical "coverage" plugin
>
> But when it does land, I promise it will be kick-ass
>
> ;-)
>
> On 29 June 2012 12:02, Mikael Petterson <mikael.petter...@ericsson.com>
> wrote:
> > Hi,
> >
> > I suspected the publishing of Cobertura coverage report taking way too
> long.
> > I upgraded from 1.3 -> 1.5 but no change ( I suspected that since
> > change list did not mention anything).
> >
> > I decided to check how long this step takes so ( after recommendation
> > from Ulli H.) I installed Timestamper ( nice plugin).
> >
> > And I found out that it takes ~ 22 minutes to publish Cobertura
> > coverage report!
> >
> > 08:19:08 Publishing Cobertura coverage report...
> > 08:41:07 Publishing Cobertura coverage results...
> >
> > Since build with tests and reports takes only 6 min I find it strange.
> >
> > I notice one difference here since we have the coverage.xml in a vob (
> > clearcase). Pattern used to Search for file is:
> >
> > *vobs/<path to cobertura xml>/coverage.xml
> >
> > Will this increase publish of report? Or is there a an operation in
> > the code below that is known to take time?
> >
> >
> > I downloaded src and tried to build 1.5 ( to be able to debug) but got
> > the following error:
> >
> > found : hudson.model.AbstractBuild<capture#336 of ?,capture#473 of
> > ?>
> > required: hudson.maven.MavenBuild
> > if(build instanceof MavenBuild) {
> > ^
> >
> /home/eraonel/git/cobertura-plugin/src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java:233:
> > inconvertible types
> > found : hudson.model.AbstractBuild<capture#515 of ?,capture#236 of
> > ?>
> > required: hudson.maven.MavenBuild
> > MavenBuild mavenBuild = (MavenBuild)build;
> > ^
> >
> /home/eraonel/git/cobertura-plugin/src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java:238:
> > inconvertible types
> > found : hudson.model.AbstractBuild<capture#919 of ?,capture#763 of
> > ?>
> > required: hudson.maven.MavenModuleSetBuild
> > } else if(build instanceof MavenModuleSetBuild) {
> > ^
> >
> /home/eraonel/git/cobertura-plugin/src/main/java/hudson/plugins/cobertura/CoberturaPublisher.java:239:
> > inconvertible types
> > found : hudson.model.AbstractBuild<capture#858 of ?,capture#685 of
> > ?>
> > required: hudson.maven.MavenModuleSetBuild
> > MavenModuleSetBuild moduleSetBu
