| Name | FindBugs plugin |
|---|---|
| Version | 2.0-beta1 |
| Product Versions | 2.0 |
| Author(s) | Stephan Paulicke |
| Maintainer | Made Mastika , James Dumay, Dushan Hanuska |
| Homepage | |
| Price | Free |
| License | BSD |
| JavaDocs | Bamboo Findbugs Plugin 2.0-beta1 |
| IssueTracking | FNDBUG |
| Subversion URL | bamboo-findbugs-plugin-2.0-beta1 |
| Download JAR | bamboo-findbugs-plugin-2.0-beta.jar |
Description/Features
A plugin that will parse and record FindBugs reports
Usage
- Copy the file into your <BAMBOO_HOME>/webapp/WEB-INF/lib directory and restart Bamboo
- In the configuration of your plan, there should be a new Findbugs section on the 'Builder Configuration' tab. Here you can specify whether your plan generates FindBugs reports, and if so, the location of the XML report file.
- The plugin will also work with maven-findbugs-plugin (recommended)
- That should be it, you should now see a FindBugs tab on your Plan and on any new builds that generate FindBugs report files.
Screenshots
|
Screenshots (view as slideshow) |
||||||
|---|---|---|---|---|---|---|
|
|
|
||||
Version History
| Version | Date | Description |
|---|---|---|
| 2.0-beta1 | 28 April 2008 | Released 2.0 compatible version to public. 1.2.x is not longer supported. |
| 1.1.2 | 12 February 2008 | fixed |
Labels
(None)
Comments (11)
Sep 03, 2007
Mark Chaimungkalanont says:
Stephan, Mate that's awesome! I'll try to check it out soon, but it looks neat ...Stephan,
Mate that's awesome! I'll try to check it out soon, but it looks neat regardless.
Cheers,
Mark C
Nov 16, 2007
Val Tarsayuk says:
I'm having problems getting this plugin to work. It installs fine, and I can see...I'm having problems getting this plugin to work.
It installs fine, and I can see that it accesses the maven-generated findbugs.xml file. But the results all display as 0 bugs, even though there are bugs recorded in the xml file. These 0 values appear as such in the database, so I believe the problem is somewhere near the initial parsing phase.
I am using Bamboo 1.2.4.
Thanks,
Val Tarasyuk
Jan 23
Made Mastika says:
Hi Val, The problem with the previous version is that it will only read findbug...Hi Val,
The problem with the previous version is that it will only read findbugs xdoc generated report which is not what FindBugs output by default. The issue has been addressed in 1.1.0 release and now it should be able to pick up the result in either xdoc or it's default xml format. I recommend you to use maven-findbugs-plugin so it'll take most of the burdens away (writing up those jelly scripts as well as compatibility with maven 2) from you. Just specify **/target/* in the output destination field, and it should work properly.
Please leave us some feedback on how to improve it.
Cheers,
Made
Mar 05
Janusz Gorycki says:
The problem I was having with this plugin was that it only failed builds on a de...The problem I was having with this plugin was that it only failed builds on a delta. Which made it not detect findbugs problems introduced together with other causes of build breakage. Also, it was possible to make a build "green" by simply re-running a failed build. This patch makes bamboo fail a build if there are any findbugs violations present. For an anal-retentive project manager like me, this is a must
Apr 29
Stephen says:
Many thanks for releasing an updated findbugs plugin for Bamboo, I was waiting o...Many thanks for releasing an updated findbugs plugin for Bamboo, I was waiting on this before migrating to Bamboo 2.
However, on my Bamboo installation the findbugs artifact copier is failling with the message "FindBugs plugin is not run because the build has failed". This is wrong, as the build has succeeded. Do you have any hints at resolving this?
May 09
Stanislaw Osinski says:
Hi, I have exactly the same problem Stephen reported (running Bamboo 2.0.1)... I...Hi,
I have exactly the same problem Stephen reported (running Bamboo 2.0.1)... I'd love to have FindBugs reports integrated, looking forward to a patch.
Cheers,
Stanislaw
May 24
Philip L. McMahon says:
I experienced the "build has failed" bug with the 2.0beta1 version, so I tried w...I experienced the "build has failed" bug with the 2.0-beta1 version, so I tried with the current code in trunk (revision 19480). I'm not a Java developer so hopefully someone with more experience can take a look at this and check my work.
I believe there are two bugs which are contributing to the issue, both in thecom.atlassian.bamboo.plugins.findbugs.FindBugsBuildProcessor class. The first is on line 97 of the source, where the currentBuildState is initially assigned – the object ends up equal to null. I'm not sure why that's happening; maybe a Bamboo developer can add some insight as to the cause.
The second issue is on line 102, where the currentBuildState object is checked for success. I believe this line should use the equals() method for comparison of the two objects.
As a test (but not a fix), I commented out the state check and the FindBugs plugin worked as expected.
May 24
Philip L. McMahon says:
I also found a bug in com.atlassian.bamboo.plugins.findbugs.actions.ViewFindBugs...I also found a bug in com.atlassian.bamboo.plugins.findbugs.actions.ViewFindBugsBuildResults, revision 19480. The serializeCsv() method can throw an uncaught NoSuchElementException on line 132 when processing a line such as "class,1,,TYPE" (where the source field is empty). I believe the StringTokenizer is skipping the empty field when parsing.
I'm attaching two patches: one for my previously mentioned "fix" for the "build has failed" bug, and one to address the CSV parsing bug.
For the StringTokenizer bug, I converted the code to use String object's split() method as suggested by the Sun 1.4.2 docs for StringTokenizer.
May 24
Stanislaw Osinski says:
I've not gone very deeply into Bambo API, but it looks like the FindBugsBuildPro...I've not gone very deeply into Bambo API, but it looks like the FindBugsBuildProcessor is invoked _during_ the build, which would mean the build status is not known yet, hence the null value (I may be wrong though -- the API says it's the partial build result...). Anyway, your "fix" might actually be a fix (without quotes
. Another hint that could confirms this reasoning is the <skipIfFailed>true</skipIfFailed> entry in the config file, which seems to do the job of the condition in the code.
Philip -- would it be possible for you to somehow make the binary you compiled available? I'd love to use this plugin without investing 2h into compiling it from sources
Thanks!
May 27
Philip L. McMahon says:
Stanislaw (and others who are interested): I attached my patched build of the Fi...Stanislaw (and others who are interested): I attached my patched build of the FindBugs plugin to this thread.
May 27
Stanislaw Osinski says:
The plugin works great now, thanks Philip\!The plugin works great now, thanks Philip!