At the previous workstation, we used external svn to update dependent projects when updating a common component. This made it easy to see all the changes that occurred as a result of these changes, as well as update project-specific projects to the latest version of the shared component without any intervention.
At the new workstation, we use cc.net with bulk scm, and I'm trying to find something like this in the environment. I did not find anything similar to the external, only "shared files", but, unlike external, shared files do not allow you to specify a specific revision of the file for the external.
I am interested in what other people do in these scenarios to rely on their continuous integration and relate more to integration than to a "continuous build" server. Does anyone know a tool or something to do "external" behavior without using svn?
I am assuming there is an xml registry file, which projects depend on which assemblies and if they should use the latest version, but this seems like superfluous.
source
share