On 7/15/2013 5:49 AM, Cooke, Mark wrote:
For your uses, perhaps you could spin this artifact off into it's own repository (use "external"s from your main repo if required) and then you can archive that repo off whenever necessary?
Sound advice for any sort of large artifact, or in the case where automated scripts will push commits into a repository on a regular (sometimes frequent) basis.
It not only keeps the size down and gives you the option to do extreme "resets" to the separate repository, but it also keeps the log history of the original repository from being polluted with all of the automated commits.
We do this on the servers that we version control using FSVS. There are sections of the directory tree which need to be heavily monitored for changes (such as configuration reports), but which don't need to pollute the main SVN repository for that machine.
