Re: yamlizing findbugs jobs
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
On Wed, Mar 9, 2016 at 2:57 PM, Sandro Bonazzola <sbonazzo(a)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)
Attachments:
- attachment.html (text/html — 3.3 KB)