kutzi
added a comment - 18/Apr/09 2:27 AM If this would help to fix this more quickly and you could point me to where I
can find this in the plugin's sources, I could have a look to prepare a patch
for this.

Ulli Hafner
added a comment - 20/Apr/09 6:59 AM Hmm, this seems to be a bug.
The new threshold is computed by:
"warnings of the current build" - "warning from last build with a findbugs result"
If the build fails then the findbugs plug-in should be skipped. Which kind of
build are you using? Is there a findbugs.xml computed for failed builds?
BTW: for the source code see
http://wiki.jenkins-ci.org/display/JENKINS/Extend+Hudson .

kutzi
added a comment - 20/Apr/09 8:26 AM > Which kind of build are you using?
Maven 2 project type with a Maven multimodule project
> Is there a findbugs.xml computed for failed builds?
I suppose so as only some child modules failed and not all.
And since the Hudson project overview displays 4 warnings for that build.
I don't know though, how to find the workspace for old builds.

Ulli Hafner
added a comment - 20/Apr/09 1:58 PM I see, for multi-module maven jobs the decision is not that easy
I'll check if there is a way in my plug-in to decide which of the modules is the root
module. Then the old and simple algorithm will still work if applied only to this root
module.