名前 |
Bamboo Change Analysis Plugin |
|---|---|
バージョン |
1.1.1 |
Product Versions |
2.0 |
Author(s) |
|
homepage |
http://confluence.atlassian.com/display/CODEGEIST/Bamboo+Change+Analysis+Plugin |
価格 |
Free |
License |
|
JavaDocs |
|
IssueTracking |
|
Download JAR |
|
Download Source |
Subversion or with Fisheye |
Description/Features
The change analysis plugin analyses each build and creates a report of all the findings. These findings include PMD, Cobertura and JMeter reports. Various quality control levels can be set in order for the build to be considered as successfull. For PMD all findings of the committed files are listed in the Change Analysis tab. A Severity threshold can be set - if any finding exceeds it the build is marked as failed. Report can be set to always include all classes in the build. Also a separate tab for all PMD findings is provided. For Cobertura line or branch rate limits (per file) can be set. Also a separate tab for all Cobertura findings is provided. For JMeter a pass rate can set. Also the build can be marked as failed if any test fail that succeeded previously. Also a separate tab for all JMeter findings is provided.
用途
- Download the CODEGEIST:jar file.
- Copy it into the 'webapp/WEB-INF/lib' directory of your Bamboo server.
- Bamboo を再起動します。
- Enable the plugin from the build plan configuration and set the approriate configurations
Version History
バージョン |
日付 |
説明 |
|---|---|---|
1.1.1 |
2008年9月21日 |
軽微な修正 |
1.1 |
2008年9月2日 |
Tab separation for reports |
1.0 |
2008 年 5 月 6 日 |
First release |
JIRA 課題
スクリーンショット
スクリーンショット |
|
|---|---|
|
|
|
Changes Tab
|
Plugin Configuration
|
11 Comments
blabloe
The PMD treshold is not working. I set the PMD treshold on errorlevel 3, but after a build wich generates only level 4 errors the build fails. Hop this can be fixed
Tatu Lahtela
I created an issue, http://developer.atlassian.com/jira/browse/BCAP-6 for this but I can't reproduce the problem without more details. Please comment your environment there. (Is the pmd tab otherwise intact etc..)
Tatu Lahtela
Or wait.. Of course the threshold is "up" that is if you set the threshold at 3 an error with severity 4 will fail the build as it is higher. If you want to ignore level 4 errors, the threshold must be 5.
blabloe
With PMD it is the other way around. An error with level 1 is more severe than an error level 4.
I gues it is somewhat confusing because we use the word "error level" as of PMD uses the word "priority". It makes a lot more sense that priority 1 issues are more important (error prone) than priority 2 issues.
Tatu Lahtela
Fascinating. That's what you get when you don't find a clear documented statement and randomly pick a few rules and try to figure out which one is more severe.. I've always had my own custom configured sets with the other way round, they're just numbers right
But you are right, I'll fix this asap.
blabloe
So that's no defcon scale
. Thnx for making a fix, any idea when this might be available?
Tatu Lahtela
I made a 1.1.1 release where this is now fixed.
Chris Hilton
Should the product versions be 2.x or something more specific? Or is this really just for Bamboo 2.0?
Tatu Lahtela
Since I'm not part of Atlassian, I can't really say what changes are meade to each future 2.x version so I can't make any guarantees. 2.0 was the version number during development and I tested against it.
The latest version has some changes that produces a non-fatal error message (the changes tab I shamelessly copied has changed), but otherwise it still works ok.
Chris Hilton
Understandable. I thought you might be using it with newer versions as they come out and it sounds like it's working okay, so I'll give it a whirl. Thanks.
Bartosz Burchard
When i check "Run change analysis per build" checkbox i have an error in the build log
(Bamboo 2.3.1)