<div dir="ltr">Isn't there a plugin like x-unit for findbugs that can just get XML file and present the graphs?<div>for the alerts on limit maybe we can implement something ourselves.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 9, 2016 at 3:21 PM, David Caro Estevez <span dir="ltr"><<a href="mailto:dcaro@redhat.com" target="_blank">dcaro@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 03/09 15:19, Eyal Edri wrote:<br>
> I think the idea is to add report.html generic file that will show anything<br>
> we'd like.<br>
> Having said that, it might be too complex or overkill to do it right now<br>
> just for findbugs, so maybe we can still use the findbugs plugin and<br>
> provide the xml file (?)<br>
> to the plugin?<br>
><br>
> Maybe we can use [1] as a generic static analysis single plugin that will<br>
> work for multiple tools?<br>
><br>
> [1] <a href="https://wiki.jenkins-ci.org/display/JENKINS/Analysis+Collector+Plugin" rel="noreferrer" target="_blank">https://wiki.jenkins-ci.org/display/JENKINS/Analysis+Collector+Plugin</a><br>
<br>
<br>
</span>This has the same issues than using each specific plugin, as it requires each<br>
of them to be configured (it just aggregates them, but does not do the<br>
result computations)<br>
<span class=""><br>
><br>
><br>
> On Wed, Mar 9, 2016 at 2:57 PM, Sandro Bonazzola <<a href="mailto:sbonazzo@redhat.com">sbonazzo@redhat.com</a>><br>
> wrote:<br>
><br>
> > About <a href="https://gerrit.ovirt.org/#/c/46925/" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/c/46925/</a><br>
> ><br>
> ><br>
</span>> > *Juan Hernandez* Mar 7 5:34 PM<br>
<span class="im HOEnZb">> ><br>
> > Patch Set 14:<br>
> ><br>
> > The only important thing that is missing is what will happen with the<br>
> > findbugs reports. Will we still have a report that tells us what bugs<br>
> > exist, what have been fixed since the last build, etc? If I understand<br>
> > correctly that is generated by the Jenkins findbugs plugin, and this patch<br>
> > doesn't use it. Will we preserve the separate findbugs job?<br>
> ><br>
> > In addition I have recently learned that the "findbugs:findbugs" mojo runs<br>
> > the checks, but doesn't fail the build if it finds issues. There is a<br>
> > different "findbugs:check" mojo that runs the check and fails the build<br>
> > with the first issue. It may be more appropriate for this purpose.<br>
> ><br>
> ><br>
> > Eyal, David, other infra members, any hint on how to progress with this<br>
> > patch?<br>
> ><br>
> ><br>
> > --<br>
> > Sandro Bonazzola<br>
> > Better technology. Faster innovation. Powered by community collaboration.<br>
> > See how it works at <a href="http://redhat.com" rel="noreferrer" target="_blank">redhat.com</a><br>
> ><br>
><br>
><br>
><br>
> --<br>
> Eyal Edri<br>
> Associate Manager<br>
> EMEA ENG Virtualization R&D<br>
> Red Hat Israel<br>
><br>
> phone: <a href="tel:%2B972-9-7692018" value="+97297692018">+972-9-7692018</a><br>
> irc: eedri (on #tlv #rhev-dev #rhev-integ)<br>
<br>
</span><div class="HOEnZb"><div class="h5">--<br>
David Caro<br>
<br>
Red Hat S.L.<br>
Continuous Integration Engineer - EMEA ENG Virtualization R&D<br>
<br>
Tel.: <a href="tel:%2B420%20532%20294%20605" value="+420532294605">+420 532 294 605</a><br>
Email: <a href="mailto:dcaro@redhat.com">dcaro@redhat.com</a><br>
IRC: dcaro|dcaroest@{freenode|oftc|redhat}<br>
Web: <a href="http://www.redhat.com" rel="noreferrer" target="_blank">www.redhat.com</a><br>
RHT Global #: 82-62605<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>Eyal Edri<br>Associate Manager<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div>
</div>