title: How to handle TeamCity dependencies for both artifacts and build triggering
body: <p>So I've got a couple of projects (A, B, C, D) where the dependencies look like this:</p>
  
  <pre><code>  B
   / \
  A   D
   \ /
    C
  </code></pre>
  
  <p>That is, B and C depend on artifacts from A, and D depends on artifacts from both B and C.</p>
  
  <p>I'd like to do a couple of things:</p>
  
  <ol>
  <li>Artifacts from previous successful builds are used in projects.  For instance, when a build for project C is triggered, it uses project A's artifacts that have been previously verified to be good (aka tests pass).</li>
  <li>Triggered builds in project also trigger builds in project that depend on them.  For instance, if a change is made in the B project, the B project is built and then the D project is built using artifacts from the just-built B project.  A change in project A rebuilds everything in this order A, B and C (concurrent), then D. </li>
  </ol>
  
  <p>I can achieve VCS triggered builds in the "Build Triggers" section.</p>
  
  <p>I can achieve artifact dependencies in the "Dependencies" section by adding an artifact dependency from "Last successful build" and pulling over my artifacts.</p>
  
  <p>I don't know how to achieve triggered builds in the correct order in the correct dependency chain.  If I make project A a snapshot dependency of project B, when B needs to be built, it rebuilds A and then rebuilds B.  Similarly, if a change happens in A, only A is rebuilt.  I would like a change in A to cause a rebuild for all my projects.</p>
  
  <p>Is this possible?  I'm on TeamCity 7.1.3.</p>