I'm having a difficult time figuring out why we seem to have a build triggering loop that causes our job queue to fill up rapidly. I'm examining our dependency settings. I'm curious about how TeamCity resolves whether a snapshot dependency is from the same revision if that dependency is in a different SCM (Subversion) repository with completely separate revision number. It seems like we have high level dependency builds that are constantly being added to the queue even though they have simple triggers that shouldn't be activated. In these cases we do have dependent projects in different repositories referencing these builds as snapshot dependencies.