Subversion space consumption... how do you cope with that?
-
Hello all, I would like to know how do you cope with the space consumption of the subversion repositories. Of course meanwhile you are developing a project it is important to keep a history of what is going on, but once it has been finished, it should be archived and all the versions should be removed except the last one. At least this is what would be interesting on my company. the only problem is that I've not been able to find any step to do that automatically. Do you do this in that way? if you do it, how? and if you don't, what do you do and why? As always, thank you in advance. :rose:
Well, if you have one project per repository, you could just delete the whole repository after making whatever backups your company deems appropriate. If you have multiple projects in a single repository, the project will still be there even if you delete the folder from the head revision. It is by design, and there's no reasonable way around that. In terms of space usage, the repository should be fairly small. A quick check of my project directories shows that the repository is less than 150% of the project directory size after 1100 revisions over 20 or so projects. As for how I do it, when a project is ready to release (a project is never finished), I simply make a tag in the repository to note which revision was used for the release. Creating a tag takes almost zero hard drive space, which is explained in the Subversion manual. I also make a folder and import the associated binaries for that release. This along with building any installers that are required for the project (which I do not import to the repository) and storing the files on the server (where all the releases from before I started using svn are stored) are all done from a script that I have developed based on my particular process. I do not know what you mean by removing "all the versions except the last one", but I definitely keep all the old revisions around. This can come in handy if you want to search through to find how you fixed a particular issue. It also is useful when trying to find out when something was changed that may not be obvious from the version release notes.
-
Hello all, I would like to know how do you cope with the space consumption of the subversion repositories. Of course meanwhile you are developing a project it is important to keep a history of what is going on, but once it has been finished, it should be archived and all the versions should be removed except the last one. At least this is what would be interesting on my company. the only problem is that I've not been able to find any step to do that automatically. Do you do this in that way? if you do it, how? and if you don't, what do you do and why? As always, thank you in advance. :rose:
As for why you want to keep your history around in some form, when you resume work on an app and are looking at a line of code going WTF!; the revision history will at least let you know what the guilty party thought it was supposed to do. If you just want to start each version of your dev with revision 1 you should be able to just import into a new repository, but this will make tracking history to older code more painful.
The latest nation. Procrastination.
-
Hello all, I would like to know how do you cope with the space consumption of the subversion repositories. Of course meanwhile you are developing a project it is important to keep a history of what is going on, but once it has been finished, it should be archived and all the versions should be removed except the last one. At least this is what would be interesting on my company. the only problem is that I've not been able to find any step to do that automatically. Do you do this in that way? if you do it, how? and if you don't, what do you do and why? As always, thank you in advance. :rose:
I do not archive anything from the repository so I do have 8 year old stuff in there. I am still using cvs though so the 2 million lines of code could fit on a single cd if needed. I believe the last time I tested moving that to svn it was less than 4GB which is pretty insignificant considering whatever server I have it on has > 2TB of raid..
John
-
Hello all, I would like to know how do you cope with the space consumption of the subversion repositories. Of course meanwhile you are developing a project it is important to keep a history of what is going on, but once it has been finished, it should be archived and all the versions should be removed except the last one. At least this is what would be interesting on my company. the only problem is that I've not been able to find any step to do that automatically. Do you do this in that way? if you do it, how? and if you don't, what do you do and why? As always, thank you in advance. :rose:
-
Hello all, I would like to know how do you cope with the space consumption of the subversion repositories. Of course meanwhile you are developing a project it is important to keep a history of what is going on, but once it has been finished, it should be archived and all the versions should be removed except the last one. At least this is what would be interesting on my company. the only problem is that I've not been able to find any step to do that automatically. Do you do this in that way? if you do it, how? and if you don't, what do you do and why? As always, thank you in advance. :rose:
For starters have differing projects in separate repositories. As for history I would probably keep the lot disk space is cheap < 10p per GB. Or archive it if necessary.
-
For starters have differing projects in separate repositories. As for history I would probably keep the lot disk space is cheap < 10p per GB. Or archive it if necessary.
David Wong wrote:
For starters have differing projects in separate repositories.
That will save an enormous amount of space with subversion.
John
-
David Wong wrote:
For starters have differing projects in separate repositories.
That will save an enormous amount of space with subversion.
John
-
I am not sure of the exact reason but I have seen the huge difference in size while testing importing cvs repositories to svn.
John
-
David Wong wrote:
For starters have differing projects in separate repositories.
That will save an enormous amount of space with subversion.
John
John M. Drescher wrote:
That will save an enormous amount of space with subversion.
I did not mean that having separate repositories would save space. I was more coming from the angle that it is easier to then archive unused repositories and delete them as opposed to what I have seen in some companies that have 1 repository and all their projects dumped into this, and wondering why the repository is so large.
-
Hello all, I would like to know how do you cope with the space consumption of the subversion repositories. Of course meanwhile you are developing a project it is important to keep a history of what is going on, but once it has been finished, it should be archived and all the versions should be removed except the last one. At least this is what would be interesting on my company. the only problem is that I've not been able to find any step to do that automatically. Do you do this in that way? if you do it, how? and if you don't, what do you do and why? As always, thank you in advance. :rose:
I go with the "disk space is cheap" and "losing information is expensive" camps.
-
I go with the "disk space is cheap" and "losing information is expensive" camps.
I admire the way that you distill thousands of words into a couple of cogent, concise bullet points. Well done. :)
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
I admire the way that you distill thousands of words into a couple of cogent, concise bullet points. Well done. :)
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
Thanks. I once had someone say that one word from me is worth ten from someone else. I think it helps my coding.