Watch one source-control location, but checkout from another?#865

Subscribe to Watch one source-control location, but checkout from another? 1 post, 1 voice

 
Avatar Pete Mounce 47 post(s) #2302

We have one (svn) repository that we keep all of our tools and libraries in, and one that we keep all of the product-code in. The product-code one looks like:
/trunk /productA /productB /external to tools and libraries to pull it all in

We’re establishing a convention for developer workstations such that they just need to do a checkout on our Products/trunk repo to get up and running. All the libraries are linked via a relative path down to the library-root directory.

It’s possible to use an environment variable when creating a reference in C# projects, but that would require a manual edit each time (there’s no way (that I know of!)) to do this via Visual Studio’s UI.

Is it possible to get Cruise to check out Products/trunk for its pipelines, but then set it up to watch Products/trunk/productA ? Or is there a different way I could approach this without introducing the friction of editing project files to insert environment variables when a library is referenced?