Cobertura merging to generic coverage plugin?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Cobertura merging to generic coverage plugin?

jxpearce
The wiki page for the Cobertura plugin says:

The current thinking is to merge this plugin into more generic coverage plugin. Help appreciated.

Is this still the current thinking? I'm interested in helping if so. We currently use Cobertura (or sometimes even HtmlPublish) for iOS and JS builds, but Jacoco for Android. A unified plugin might make things simpler.

Jeff 

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b7235184-63c9-4b17-be03-c8667a8b39cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Cobertura merging to generic coverage plugin?

Jesse Glick-4
On Tue, May 9, 2017 at 10:55 AM,  <[hidden email]> wrote:
> Is this still the current thinking?

Probably that thinking was thought by Stephen Connolly several years
ago, but yes that sounds like a good plan if it is feasible. Does not
sound like an easy refactoring.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2bcWeO9Xj%2BfpM-w0-qcXHyL6mwpvPVLgnvx7Z02j-hdg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Cobertura merging to generic coverage plugin?

Oleg Nenashev
Added Steven Christou and James Dumay to Cc.

I agree some refactoring and generalization (e.g. via Coverage API Plugin) will be really useful, especially since shuch generic APIs may be required soon when and if BlueOcean starts supporting coverages in its UIs. On the other hand it is still a big effort investment if you want to do it correctly and to integrate other coverage plugins (Emma, JaCoCo, Clover, etc.).

So we need to understand who is ready to drive it first.

BR, Oleg

вторник, 9 мая 2017 г., 21:16:45 UTC+2 пользователь Jesse Glick написал:
On Tue, May 9, 2017 at 10:55 AM,  <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="3qy8EIoVAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jxpe...@...> wrote:
> Is this still the current thinking?

Probably that thinking was thought by Stephen Connolly several years
ago, but yes that sounds like a good plan if it is feasible. Does not
sound like an easy refactoring.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1fcc2a5d-af73-4568-a208-b3cca36b2aab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Cobertura merging to generic coverage plugin?

Oleg Nenashev
I'd guess this thread is now revived, because we have such project in GSoC 2018: https://jenkins.io/projects/gsoc/2018/code-coverage-api-plugin/

See https://groups.google.com/forum/#!topic/jenkinsci-dev/A7KtzQSp1vQ

On Monday, May 22, 2017 at 11:37:59 AM UTC+2, Oleg Nenashev wrote:
Added Steven Christou and James Dumay to Cc.

I agree some refactoring and generalization (e.g. via Coverage API Plugin) will be really useful, especially since shuch generic APIs may be required soon when and if BlueOcean starts supporting coverages in its UIs. On the other hand it is still a big effort investment if you want to do it correctly and to integrate other coverage plugins (Emma, JaCoCo, Clover, etc.).

So we need to understand who is ready to drive it first.

BR, Oleg

вторник, 9 мая 2017 г., 21:16:45 UTC+2 пользователь Jesse Glick написал:
On Tue, May 9, 2017 at 10:55 AM,  <[hidden email]> wrote:
> Is this still the current thinking?

Probably that thinking was thought by Stephen Connolly several years
ago, but yes that sounds like a good plan if it is feasible. Does not
sound like an easy refactoring.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cd7bf7bc-eb2a-4332-9b6d-68b8d66374f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.