Report Aggregation

compared with
Version 15 by Steve Luo
on Jun 22, 2011 16:20.


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.

 h3. What is report aggregation
 The report aggregation is used to collect and aggregate the build metrics from a child configurations or itself. Whether or not a configuration will aggregate the metrics depends on your aggregation setting. For example, we have configuration tree like below, and define a JUnit aggregation in ROOT configuration:
  
 {code}
  + ROOT
  |
  +---+ QuickBuild
  |
  +------+ V3.x
  |
  +---------+ DEV
  |
  +---------+ INTEGRATION
  |
  +------+ V4.x
  |
 {code}
  
 after finishing building configuration _ROOT/QuickBuild/V3.X/DEV_, the tests related metrics will be collected and aggregated to _DEV_ itself, then go up to configuration _V3.X_, then continue to _QuickBuild_, and finally to _ROOT_. When go to the configuration overview tab, a _Recent JUnit Tests_ panel is displayed and it contains the tests information of the build:
  
 !aggregation1.png!
  
 after finishing building configuration _ROOT/QuickBuild/V3.X/INTEGRATION_, the same process will be taken place, and a new row is added to the table like:
  
 !aggregation2.png!
  
 In the table above, each row shows the metrics of the latest build of a configuration, that is, when you run configuration _ROOT/QuickBuild/V3.X/DEV_ again, the entry for it will be replaced to the new build _1.0.1_.
  
 and in statistics page, a tab 'JUnit Aggregated' displays the trends of the aggregated metrics and you can group by day, by week and by month.
  
 h3. How to define aggregation
 To define aggregation is very straightforward. Go to configuration setting page and select Aggregations tab, then add an aggregation you want, you need input the aggregation name and aggregation condition. The report set field is used to tell QuickBuild you only want to aggregate some specific report sets, if leave empty, QuickBuild aggregates all available report sets.
  
 You may define the aggregations as more as you want by specifying the aggregation condition and report set, for example, you may define an aggregation which only aggregates all the metrics from all DEV configurations, and define another to aggregate from all INTEGRATION configurations.
  
 Just like all other configuration settings, the aggregation setting can be inherited/overridden from its parent.
  
 h3. Add aggregation gadget
 You may also add the aggregation gadgets to the dashboard, so you can know the status of a configuration at first glance.
   
 !tests.png!