Independant parallel builds

Hi,

we are facing a nasty problem. We have quite a complex setup:

- We are building packages for different OSes (each and every OS has it's own Build Config)
- The OS builds are derived from custom Linux and Windows build templates
- We have a global build counter build config so that to have one single version number for every built packages
- We have a build package template which snapshot depends all the OS build configs and thge global build counter as well
- The build package template has 3 reverse.dep.* argument which comes from "outside", those define like the name of the product,
the GIT branch we need to built out of, and the git URL of the package
- We have various individual build configs templated from the "Build Package" template setting via reverse.dep.* the required parameters

All of the above works just fine until I build one single package. However we wish to have a "group build config" which "groups" different individual packages (let's say 6 packages) and the expected outcome is that if I press "Run" on this build config, all the individual packages (most probably in parallel) needs to be built, and the outcome of the "aggregate" build considered success in case all the individual packages are built successfully. 

I have tried to create this via snapshot dependency, however in this case when I run the build, the individual OS builds are not started as they receive all the 6 individual packages reverse.dep.* configuration parameters at once and they end up in a "conflict" with each other.

So what I'm after is a kind of "batch build", e.g. to be able to trigger the individual build configs - which are practically independant from each other - like if I execute the individual package builds one after the other via 6 times pressing the "Run" button on the different package build configs.

Thanks,
Tibor