I am trying out TeamCity 4.5 EAP and the situation I have is that I am trying to efficiently share a Perforce VCS root that contains a large amount of content (over 2GB of data) between multiple build configurations. I have been browsing through the discussions but I haven't found any real similar situation to the one that I am trying. What I would like is for the VCS root to be synced to the latest rev once and then it never has to be cleaned and only updated as infrequent changes are made. Now, I have tried a couple of different situations. First, I added this VCS Root (lets say VCS1) alongwith the VCS root that builds my software in a build configuration (VCS2). This does serve my purposes well, as it works across build agents and only does one get of VCS1 until I want to clean the checkout directory, because I would only like to clean the source for VCS2 but not VCS1 since VCS1 is large and takes time to sync from clean. Thats where this option breaks down. So then I tried adding a separate build configuration that syncs VCS1 and make the rest of my software builds depend on that. The problem with that is if a downstream project that depends on VCS1 is sent to a different build agent, then that build configuration for VCS1 may not have been run on the other agent, making the dependant files missing.
So after all this, my question is, is there a better way for me to be able to get the desired behaviour? I am still tinkering with this to get it to work just right, and I would really appreciate some suggestions.
Thanks in advance