Report Aggregation

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:

  + ROOT
  |
  +---+ QuickBuild
  |
  +------+ V3.x
  |
  +---------+ DEV
  |
  +---------+ INTEGRATION
  |
  +------+ V4.x
  |

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:

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:

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.

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.

Just like all other configuration settings, the aggregation setting can be inherited/overridden from its parent.