Is there anyway to group configs to stop them runningconcurrently?
Without having to put all into one great build config.
A basic example:
Version control check-in causes Config A to trigger and App A be built.
Config Atriggers Config B to deploy App A
Config Btriggers Config C to run tests against App A
Version control check-in causes Config 1 to trigger and App 1 be built.
Config 1triggers Config 2 to deploy App 2
Config 2triggers Config C to run tests against App 1
WhenConfig C is running we don’t want Config B or 2 to run as it will disrupt thesystem testing.
This is just one example…
So we just need a way to group the configs together so theyare always run sequentially even if agents are free.I believe this issomething done in other build software; just not sure how to do it in TeamCity. I think that the equivalent in CruiseControl is build queues, they have multiples of these which means only one thing in each build queue gets built at a a time.