Re: [JENKINS] important change in findbugs analysis
----- Original Message -----
From: "Roy Golan" <rgolan(a)redhat.com>
To: infra(a)ovirt.org
Sent: Sunday, January 27, 2013 2:06:40 PM
Subject: Re: [JENKINS] important change in findbugs analysis
On 01/27/2013 11:57 AM, Eyal Edri wrote:
> fyi,
>
> as part of the efforts to reduce bugs found by findbugs jenkins
> job,
> NORMAL priority bugs limit has been set to 15 (current count),
> this means that any NEW NORMAL bugs that will enter ovirt-engine
> code will fail the job,
> and it's the committer responsibility to fix it.
>
> if you're not sure about your code, you can run mvn
> findbugs:findbugs before merging (there's also an eclipse plugin
> for it).
>
> there is on-going work on reducing NORMAL bugs, and this limit will
> reduce in the near future,
> until it will reach '0' (similar to HIGH prirority).
how do we keep track of find bugs issues and assign them to
developers
to solve?
1.All current findbugs in NORMAL priority are already assigned to asaf, and he's
working on them.
2.Any newey introduced bug (either HIGH or NORMAL) will have to be fixed quickly by the
committer that introduced it.
similar to a unit test failure.
> thanks for the cooperation.
>
> Eyal Edri
> oVirt infra team.
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra