On 03/09 15:28, Eyal Edri wrote:
> Isn't there a plugin like x-unit for findbugs that can just get XML file
> and present the graphs?
> for the alerts on limit maybe we can implement something ourselves.

There is, the issue is that if that xml file does not exist it fails the job,
so it's not good to be added to the ci-standard

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

--
David Caro

Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D

Tel.: +420 532 294 605
Email: dcaro@redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605