Import an existing Subversion repository 2
To upload the history of an existing Subversion repository, use the svnsync tool that ships with Subversion 1.4. Run svnsync help to see the help for this tool.
Note that your Code Spaces Subversion repository must be at revision 0 to perforn a sync operation, so create a new repository if you need to.
Here’s a sample transcript that demonstrates how you can import the history from an existing repository (located at file:///c:/path/to/localrepos) to your repository on Code Spaces:
Windows:
C:\> svnsync init --username YOURUSERNAME https://svn.codespaces.com/YOURACCOUNT/YOURREPOSITORY file:///c:/path/to/localrepos
Copied properties for revision 0.
C:\> svnsync sync --username YOURUSERNAME https://svn.codespaces.com/YOURACCOUNT/YOURREPOSITORY
Committed revision 1.
Copied properties for revision 1.
Committed revision 2.
Copied properties for revision 2.
[...]
OSX or Linux:
$ svnsync init --username YOURUSERNAME https://svn.codespaces.com/YOURACCOUNT/YOURREPOSITORY file:///path/to/localrepos
Copied properties for revision 0.
$ svnsync sync --username YOURUSERNAME https://svn.codespaces.com/YOURACCOUNT/YOURREPOSITORY
Committed revision 1.
Copied properties for revision 1.
Committed revision 2.
Copied properties for revision 2.
[...]
When prompted for your password, use your Code Spaces password.
Running svnsync on a large repository will take a significant amount of time. If you are disconnected during the process, you may see the error message “svnsync: Couldn’t get lock on destination repos after 10 attempts”. If this happens, you can remove the lock yourself, see the “Locks” section of svnsync.txt.
Categories
CodeSpaces.com
Code Spaces is an online development and collaboration service that includes: Subversion Hosting, Project Management, Work Items, Forums, and much more.
Syndicate
Archives
- September 2010
- August 2010
- July 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
Great post. I don’t know if you have this tip in Code Spaces itself. I would have this as one of the very first things you seen when you create an account. Most of your users (like myself) probably already have an SVN repository somewhere that they want to move over. Now a quick google search probably would have found it, but for some reason I didn’t think of that. Lets just say I used suboptimal way of doing it.
Good point Chris, I will add some info about this inside the application itself :-)