Re: Active SVN Working Folder is getting too big!
From: Aric Czarnowski <aczarnowski_at_unimax.com>
Date: Wed, 7 Jun 2017 13:46:27 +0000
> Sam <sameer.premji_at_gmail.com>
Could you expand on what the single SVN repository holds? Is this truly a single tool with 10GB of sources or all the tools in your organization in their own sub directories?
If the later, converting each to their own repo is the solution. I untangled a similar situation in my organization and it was absolutely worth the pain. Certainly, do not add additional tools going forward. Create an SVN repo per tool.
Are there a significant number of binaries; images, MS Office files, etc.? Could any of these be built from lighter sources instead of stored in the repo?
For example, we have support EXEs used in our main tool's build system checked into our repo against my preference. The cost of giving everybody the environment to create these support EXEs from their sources isn't worth the decreased repo size. But with 10GB working copies your compromise might be different.
Are there third party packages checked in that could be pulled dynamically? Converting to tools like NuGet, npm, bower - the equivalent for your environment if any exists.
> we do not want to lose the history as well as there are some folders/files (code)
This implies you might be keeping sources in the working copy that are not currently used as a sort of reference? If true, stop. Tag the repo and SVN delete this stuff. Do not carry this baggage in every working copy. SVN allows you to go back and review when needed. That's what version control systems are made for.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
This is an archived mail posted to the TortoiseSVN Users mailing list.