History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-2887
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Robin Shen
Reporter: J. Mash
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
QuickBuild

QuickBuild Aggregation Enhancement

Created: 28/Jan/17 12:46 AM   Updated: 28/Jan/17 12:46 AM
Component/s: None
Affects Version/s: 7.0.0, 7.0.1
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
Currently, when you go through the process of setting up a report aggregation, you are presented with the option to specify the 'Builds to be Aggregated'. There are many options here that are all very useful, but seems to be missing support for one of the core components of the QuickBuild configuration tree -- Triggered builds.

Consider a configuration tree that is set up something like this:

    /root/project/branch/Dev
    /root/project/branch/Main

    /root/project/pipeline/build
    /root/project/pipeline/build/darwin
    /root/project/pipeline/build/redhat
    /root/project/pipeline/build/windows
    /root/project/pipeline/prove
    /root/project/pipeline/release

The "branch" configurations are literally wrappers with some data (variables) that are used to trigger the "pipeline" configurations, which do all the work. It would be extremely convenient to be able to specify something
 
  -- Aggreate builds from all **triggered** configurations.

To have it automatically figure out the builds to aggregate based on what other configurations were triggered.


 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.