Sonar is in my opinion evil esp when used with maven projects. Maybe things gaffe changed on the post few years but anything that makes a build not reproducible gets left at the door
On 3 February 2015 19:33:12 GMT+00:00, Kanstantsin Shautsou <[email protected]> wrote: >Do you have comparison list why sonar is better? AFAIR sonar has >unclear >old history while jenkins store exact to builds history. > >On Sunday, February 1, 2015 at 2:39:55 PM UTC+3, Stephen Connolly >wrote: >> >> Send too soon >> >> On Sunday, February 1, 2015, Stephen Connolly ><[email protected] >> <javascript:>> wrote: >> >>> Many years ago, I was working for a company and we were asked to >report >>> on test coverage... >>> >>> So I wrote the clover plugin... >>> >>> Then we ha a new corporate standard pushed from on high, so I wrote >the >>> Cobertura plugin >>> >>> Then people started to complain when their 75mb coverage reports did >not >>> work >>> >>> And corp wanted complete coverage including c++, .net, etc >>> >>> Then launched an effort to unify the three Java coverage plugins, >that >> dragged me off writing maven plugins, and lots of other things >> >> Sonar is probably a better solution for this space but at some stage >*if* >> I ever get time I will work on this again... >> >> It's an interesting and hard problem >> >>> >>> >>> On Saturday, January 31, 2015, Surya Gaddipati ><[email protected]> >>> wrote: >>> >>>> I saw the following statement on the wiki page for cobertura >pluggin >>>> >>>> "The current thinking is to merge this plugin into more generic >>>> coverage plugin. Help appreciated." >>>> >>>> https://wiki.jenkins-ci.org/display/JENKINS/Cobertura+Plugin >>>> >>>> I was wondering how I can help with that effort. I am interested >in >>>> generic coverage plugin that would enable me to develop tools on >top of >>>> it,. >>>> >>>> Surya >>>> >>>> -- >>>> 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 [email protected]. >>>> To view this discussion on the web visit >>>> >https://groups.google.com/d/msgid/jenkinsci-dev/971fb21f-92d9-4436-aed4-2ce742a80d71%40googlegroups.com > >>>> ><https://groups.google.com/d/msgid/jenkinsci-dev/971fb21f-92d9-4436-aed4-2ce742a80d71%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> >> >>> >>> >>> -- >>> Sent from my phone >>> >> >> >> -- >> Sent from my phone >> > >-- >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 [email protected]. >To view this discussion on the web visit >https://groups.google.com/d/msgid/jenkinsci-dev/76ff2539-25e8-4b6d-af83-5aa2abb50b7d%40googlegroups.com. >For more options, visit https://groups.google.com/d/optout. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C1F5B5E1-D570-46CC-AEED-4FB8207B117A%40teilo.net. For more options, visit https://groups.google.com/d/optout.
