I am always too busy to solve the hard blocking problem: merging coverage results from different toolchains...
I have some ideas, but it is always on the back burner. Also, basing on cobertura is a mistake. There were some design decisions I made in that plugin's architecture that in retrospect were a mistake. On Monday, 5 August 2013, Manu wrote: > Hi, > > I think that, a while ago, there was a discussion about implementing a > universal code coverage plugin, based on the cobertura plugin, but that > would be able to parse code coverage results from quite a few other tools > (see > http://jenkins-ci.361315.n4.nabble.com/Re-Hudson-cobertura-plugin-td379075.html > and > other pages). > > Do you know if there has been any work on this ? It doesn't seem to be > finished for sure, because I couldn't find any "coverage" plugin on Jenkins. > > The reason I am asking is that I could try to help build it. > > Thanks > > Manu > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:_e({}, > 'cvml', 'jenkinsci-users%[email protected]');>. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Sent from my phone -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
