If the output it retained within the Jenkins job workspace then we can at least look into it. Would be a good point of reference for developers.
On Thursday, October 15, 2015, Tom Barber <tom.bar...@meteorite.bi> wrote: > Hi Lewis, > > No problem, I thought about adding it to Jenkins but I don't think we > publish the site docs automatically currently, so there is little point. If > someone knows how we can publish the site docs after each build, then yes > it would be great to add it to the jenkins build. > > Tom > > On Thu, Oct 15, 2015 at 4:13 PM, Lewis John Mcgibbney < > lewis.mcgibb...@gmail.com <javascript:;>> wrote: > > > Nice Tom. > > Will add the directions to the website documentation as I think there is > an > > area for eat coverage. > > We adding this to the Jenkins build yes? > > > > On Thursday, October 15, 2015, Tom Barber <tom.bar...@meteorite.bi > <javascript:;>> wrote: > > > > > Okay they sent me the new license, its in our root pom.xml but doesn't > > have > > > any effect on the build, you need to run it manually: > > > > > > mvn clover2:setup test clover2:aggregate clover2:clover > > > -Dmaven.test.failure.ignore=true > > > > > > for example and it will report to the site folder. > > > > > > The plugin is in the committers donated licenses folder in SVN, it is a > > > license for org.apache.* so if you want to use it on another project to > > use > > > the same license. > > > > > > Tom > > > > > > On Thu, Oct 15, 2015 at 6:57 AM, Lewis John Mcgibbney < > > > lewis.mcgibb...@gmail.com <javascript:;> <javascript:;>> wrote: > > > > > > > Sound > > > > > > > > On Tue, Oct 13, 2015 at 12:37 PM, Tom Barber < > magicaltr...@apache.org <javascript:;> > > > <javascript:;>> > > > > wrote: > > > > > > > > > Okay, had a bit of a search of the mailing list archive and found a > > > > Clover > > > > > license, so I added it to the pom, sadly its out of date! > > > > > > > > > > I'll check with Atlassian and see if we can get a renewal, the old > > one > > > > was > > > > > licensed for all org.apache.* packages so all projects could use > it, > > > > > hopefully we can get another one the same. > > > > > > > > > > Tom > > > > > > > > > > On Sun, Oct 11, 2015 at 9:51 PM, Tom Barber < > tom.bar...@meteorite.bi <javascript:;> > > > <javascript:;>> > > > > > wrote: > > > > > > > > > > > Yeah I use the clover report all the time in real life and its > > great > > > > for > > > > > > stuff like OODT but its an Atlassian product, so I just ran it on > > my > > > > > laptop > > > > > > using my own open source license. Technically we would qualify > for > > an > > > > > open > > > > > > source license, but I don't know what the ASF policy is, or, they > > > might > > > > > > already have a license in which case, absolutely, its just > > published > > > > with > > > > > > the standard Maven Site. > > > > > > > > > > > > If no one else knows, I can check with Infra, Sonar also is > > supposed > > > to > > > > > > have code coverage but its not visible so I don't know if they > > > disable > > > > > it, > > > > > > also Clover reports can be used by Sonar, so there is some > > crossover > > > > > there. > > > > > > > > > > > > Tom > > > > > > > > > > > > On Sun, Oct 11, 2015 at 9:48 PM, Lewis John Mcgibbney < > > > > > > lewis.mcgibb...@gmail.com <javascript:;> <javascript:;>> wrote: > > > > > > > > > > > >> This is also extremely useful. How did you generate the report? > > Can > > > we > > > > > >> automate this as part of builds against master? > > > > > >> > > > > > >> On Saturday, October 10, 2015, Tom Barber < > > tom.bar...@meteorite.bi <javascript:;> > > > <javascript:;>> > > > > > >> wrote: > > > > > >> > > > > > >> > On top of the Sonar stuff, I ran Atlassian Clover over the > whole > > > > > >> project to > > > > > >> > get some coverage stats. > > > > > >> > > > > > > >> > The results of which you can find here: > > > > > >> > http://www.meteorite.bi/downloads/clover/ > > > > > >> > As you can see we currently stand as 26% coverage. Handily the > > > > clover > > > > > >> > report tells us some stuff about what's missing. So on top of > > > > cleaning > > > > > >> up > > > > > >> > the code, I can finally look at adding to the test suite. > > > > > >> > > > > > > >> > Tom > > > > > >> > > > > > > >> > > > > > >> > > > > > >> -- > > > > > >> *Lewis* > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > *Lewis* > > > > > > > > > > > > > -- > > *Lewis* > > > -- *Lewis*
