title: Teamcity - Monitoring a specific folder as a VCS trigger
body: <p>We are moving to a monolithic repository for a project which means that when a commit occurs, on team city we need to determine which build to kick off.</p>
  
  <p>Consider the following repo:</p>
  
  <pre><code>/
    a/
    b/
  </code></pre>
  
  <p>We currently have builds per sub-project that need to trigger when commits </p>
  
  <p>In VCS triggers, we can create a VCS trigger rule, which "seems" to work however I have the following questions:</p>
  
  <ol>
  <li>if I commit a change to folder <code>b</code>, through a trigger rule I can make only the builds for <code>b</code> kick off.  However, the builds for <code>a</code> show pending changes that are unrelated.</li>
  <li>Is this approach sensible long term?  Are there any unintended gotchas that occur?</li>
  </ol>