title: TeamCity build dependencies and choosing the correct branch
body: <p>I have a single project with three build configurations:</p>
  
  <ol>
  <li>Integration </li>
  <li>Deploy Dev </li>
  <li>Deploy Release</li>
  </ol>
  
  <p>Build configs 2 and 3 are dependent on 1 via a snapshot.</p>
  
  <p>There are 3 VCS roots:</p>
  
  <ol>
  <li>Git - All (used with build config 1)</li>
  <li>Git - Develop (used with build config 2)</li>
  <li>Git - Master (used with build config 3)</li>
  </ol>
  
  <p>The default branch and branch specs are as follows:</p>
  
  <p><strong>Git - All</strong></p>
  
  <p>default branch: </p>
  
  <blockquote>
    <p>develop</p>
  </blockquote>
  
  <p>branch spec: </p>
  
  <blockquote>
    <p>+:refs/heads/(develop)<br>
    +:refs/heads/(master)<br>
    +:refs/heads/(feature/<em>)<br>
    +:refs/heads/(hotfix/</em>)<br>
    +:refs/heads/(release)<br>
    +:refs/heads/(support/*)  </p>
  </blockquote>
  
  <p><strong>Git - Develop</strong></p>
  
  <p>default branch: </p>
  
  <blockquote>
    <p>develop</p>
  </blockquote>
  
  <p>branch spec: </p>
  
  <blockquote>
    <p>+:refs/heads/(develop)  </p>
  </blockquote>
  
  <p><strong>Git - Master</strong></p>
  
  <p>default branch: </p>
  
  <blockquote>
    <p>master</p>
  </blockquote>
  
  <p>branch spec: </p>
  
  <blockquote>
    <p>+:refs/heads/(master)  </p>
  </blockquote>
  
  <p>Here is the problem...</p>
  
  <p>When I run a build for the third build config, I want the dependency to check for integration builds on the master branch. It is not doing and will always use the default branch of the integration build config (currently develop).</p>
  
  <p>Is there a way to achieve what I want?</p>
  
  <ul>
  <li>Have a single integration build config</li>
  <li>Have a separate build config that is dependent on only develop branch updates</li>
  <li>Have a separate build config that is dependent on only master branch updates</li>
  </ul>
  
  <p>The way I have done it in the past involved using multiple CVS end points on a single build config, which also seems wrong and I wanted to avoid that if possible.</p>