I have the following configuration:
where Configuration B has a Snapshot and an Artifact Dependency on Configuration A. I also have the "Build from the same chain" item selected. I also have "Trigger on changes in snapshot dependencies" checked on Configuration B. I'm using TFS 2010.
Here is what I think is happening:
1. I check-in changes to TFS for both Configuration A and Configuration B within the same changeset.
2. TeamCity see's that changes have been made to Configuration A and queues a build.
3. TeamCity see's that changes have been made to Configuration B, then sees that since there's a dependency on Configuration A and queues a build for Configuration A.
4. TeamCity finally queues a build for Configuration B.
So after this, the build queue looks like this:
Because I have 2 build agents, Configuration B is built on each of the build agents at the same time.
Is there a way to make TeamCity smart enough to see that the code was part of the same changeset and not to queue Configuration A twice?