title: Moving files between build chain builds
body: <p>What is the set up required to move files between builds in TC? I am needing to move both modified source files and build binaries between the build configurations of a build chain.</p>
  
  <p>I have 1 project with 4 builds. The builds are </p>
  
  <ol>
  <li>Update Version Number (This build updates 15 sources files)</li>
  <li>Compile (This build compiles a dozen objects)</li>
  <li>Test (This build runs a regression test)</li>
  <li>Create Package (This build creates a setup.exe file)</li>
  </ol>
  
  <p>Information about the TC setup and chain</p>
  
  <ul>
  <li>I am using perforce as my VCS.</li>
  <li>All 4 builds use the same VCS root.</li>
  <li>On all 4 builds under version control settings I have "Clean all files before build" set to "On". </li>
  <li>"Update Version Number" build is triggered by any check in to the VCS. (This works)</li>
  <li>I have been able to successfully chain and trigger the builds. However each build starts with a fresh copy of files from the VCS.</li>
  <li>The chaining is set up to use snapshot dependency. </li>
  </ul>
  
  <p>Based off of the <a href="https://confluence.jetbrains.com/display/TCD10/Build+Dependencies+Setup" rel="nofollow noreferrer">TC documentation</a> it looks like I should be using snapshot dependency and not artifact dependency. If I put the build steps of all the builds into the same build everything works. However we are looking to have more flexibly and expand on this build chain in the future.</p>
  
  <p>I tried setting up the configuration so only the first build is attached to the VCS root and the other builds don't have any VCS root. This didn't work. </p>
  
  <p>I have been unable to find the answer googling but I have been able to find <a href="https://teamcity-support.jetbrains.com/hc/en-us/community/posts/206853945-Chaining-builds-top-down" rel="nofollow noreferrer">someone else who is struggling with this problem</a>. Sadly they didn't receive an answer.</p>