we use TC heavily but due to our builds taking long time I was trying to figure out what can be changed to improve it. Appears that some of our Build Configuration were building the same stuff. For example, we have these build configs: [Windows, WindowsTests, WindowsTestsFull, Xbox, Android, iOS, Mac]. These run obviously on different machines and so do WindowsTests and WindowsTestsFull. WindowsTests or WindowsTestsFull each take over 20 minutes to complete and temporary build object files and binaries are like 5GB-10GB. It appears that in both of these configs they build pretty much the same stuff, which ads extra weight on our buildfarm and out of 20+ minutes of the total execution time 18 minutes or so are taken by tests that run sequentially and aren't using multiple cores.
Obvious solution is to 1) combine two build configs WindowsTests and WindowsTestsFull into one TC build config (this way we don't build the same stuff twice using two different machines) and then 2) run tests in parallel on that same machine that built them. Build steps for this combined WindowsTests config would be something like Build test1, build test2, build test3, ... build testN, then sequentially run these tests. Some of the tests take over 5 minutes and aren't CPU intensive and we would like to run them in parallel on the same PC. How can I do that, so that we could perhaps even see that green bar per each sub-config of our WindowsTests config? If not green bar then at least some way to do that where logs can be checked separately?