View Source

h1. Scenario
Setup a configuration to act as dashboard of other configurations: it should reflect status of latest build of selected configurations, as well as aggregate various reports from those configurations.

h1. Demonstration
Please visit [the demo aggregate configuration|]. It acts as dashboard of its child configurations:
* Status of this configuration is successful only if all its child configurations built successfully; otherwise, the failed configurations will be displayed.
* For demonstration purpose, it is configured to only aggregate JUnit reports generated by child configurations. Various indicators such as success rate, test duration is the merge result of child test reports, and [the package view|] displays packages coming from the child configurations, respectively _org.apache.commons.collections_, and _org.apache.commons.configuration_. Report statistics will reflect this aggregation as well.

h1. Resolution
# For each configuration need to be aggregated, add steps to publish report XML files as artifacts. Taking the [commons-collection|] for example, the step _publish junit xml reports_ is created to publish JUnit report xml files as artifacts.
# In the aggregation configuration, [set up QuickBuild repositories|] to checkout desired report xml files from desired configurations. When define these repositories, please make sure the _build_ property is defined as _latest build_.
# In the aggregation configuration, [set up steps|] to:
## Checkout from QuickBuild repositories defined above.
Checkout step will fail if corresponding configuration fails to build.
## Publish desired reports using all retrieved report xml files.
# Edit [general setting|] of the aggregation configuration to set a periodical build schedule. With this setting, the aggregation configuration will build automatically to aggregate build status and reports if there are new builds generated in corresponding configurations.