5. Publish Build Reports

Version 26 by Steve Luo
on Aug 24, 2008 20:02.

<< Changes from 25 to 26
compared with
Version 27 by Steve Luo
on Aug 24, 2008 20:07.

Changes from 27 to 28 >>
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 1 changes. View first change.

 h2. Introduction
 Build reports are very important for detecting the project health. Via adding your build reports to QuickBuild, the project health can be tracked very easily, and the most important thing is that QuickBuild can collect the statistics data from those reports, and this will help you to analyze the project from [build statistics|3. Working with Statistics] later.
  
 Below screenshot shows a typical Java project overview by adding some reports to QuickBuild:
 !buildOverview.png!
  
 h2. Supported Reports
 Below table lists the all reports which QuickBuild support in nature:
 h3. Java Category
 ||Report Name ||Version ||
 |[JUnit Report|5.5 Adding JUnit Report]| 3.8+ |
 |[CheckStyle Report|5.1 Adding CheckStyle Report]| |
 |[EMMA Report|5.2 Adding EMMA Report]| |
 |[PMD Report|5.7 Adding PMD Report]| |
 |[Ivy Dependency Report|5.4 Adding Ivy Dependency Report]| |
  
 h3. .NET Category
 ||Report Name ||Version ||
 |[NUnit Report|5.6 Adding NUnit Report] | 2.0 |
 |[MBUnit Report|5.7 Adding MBUnit Report]|2.4+|
  
  h3. Generic Reports
 For those reports we haven't supported, you can also leverage the abilities of QuickBuild by adding [HTML reports|6. Publish HTML Reports] or by adding [generic statistics reports|5.3 Adding Generic Statistics Report].
  h3. Third-Party Reports
 For those reports we haven't supported directly, you can also [create your own plugin setting|Customizing the Build Report] of the plugin com.pmease.quickbuild.plugin.report.generic to publish the reports, or you can also create your own plugin to meet your requirements.