Same working copy of the code with 2 SVN servers

Question

Is it possible to use same working copy and to put the same into two different SVN servers(commit, update,...)?

Good question, +1, you'd be surprised how many people have to do this for one reason or another. — Tim Post, Mar 03 '09 at 07:49

Pawel Krakowiak · Answer 1 · 2009-03-04T08:06:16.543

3

Yes, you can use the Relocate (thanks, Peter) command to connect your working copy with the first repository, commit there, and then relocate to the second repository and commit there as well. Better make a copy of your working copy folder somewhere else first.

edited Mar 04 '09 at 08:06

answered Mar 03 '09 at 07:39

Pawel Krakowiak

9,300
2
33
54

1

I'm getting 'Repository UUID doesn't match' error :( – Saneef Mar 03 '09 at 11:14
Are the login credentials different for the repositories? – Pawel Krakowiak Mar 03 '09 at 11:25
This is not working ! Each repository has its own UUID so you cannot switch --relocate to a new URL which is a different Repository. except you manipulate the uuid to match(which is not a good thing to do) – Peter Parker Mar 03 '09 at 12:17
I think you're right, Relocate is the right thing to do. – Pawel Krakowiak Mar 04 '09 at 08:05
1

For me 'Relocate' is also giving UUID problem :( – Saneef Mar 06 '09 at 06:16
Are you relocating to the same repository on two different servers? I think not, it looks like what you're trying to do is to relocate to a totally different repository (that was created separately, not copied) - then I guess you can't do that. – Pawel Krakowiak Mar 06 '09 at 07:39

score 3 · Accepted Answer · edited May 23 '17 at 11:48

3

How to synchronize two Subversion repositories?

Can I have one project in two SVN repositories?

SVN: one working copy, two repositories?

edited May 23 '17 at 11:48

Community

1
1

answered Mar 03 '09 at 07:57

Zoredache

31,819
7
40
59

score 1 · Answer 3 · answered Mar 03 '09 at 07:39

If multiple people would be talking to different svn servers, you'll have trouble. The two servers won't talk to each other to make sure they don't have conflicts, use the same revision numbers etc. At least, I don't know of any svn hacks that will do this. (There are other distributed version systems based around svn, such as svk.)

What's the core goal here? Can you only push to a single server, but then have a post-commit hook to replicate the change to another server, which would allow easy read-only access from the other location?

The more details you can give about what you want to do, the more likely we are to be able to help you.

score 1 · Answer 4 · answered Mar 03 '09 at 07:41

1

Distributed version control systems, such as Mercurial, Bazaar or Git are better suited for such tasks. You can push you changes in any number of repositories.

answered Mar 03 '09 at 07:41

Eugene Morozov

13,126
3
23
31

score 1 · Answer 5 · answered Mar 03 '09 at 07:48

Its possible but horribly racy. I currently have to do that because my ISP is brain dead and I have a hard problem reaching various data centers in Europe. So, I push to my server in Canada which immediately pushes to the real repository.

On two occasions, I actually ended up with a different revision number (+1), which means my next svn up became very interesting.

So, I just used SSHFS (a FUSE mount) to edit files in place on the Canada copy, then committed directly. Its still a real pain and one of the many reasons why I love Mercurial so much.

score 0 · Answer 6 · answered Apr 24 '14 at 14:13

First, checkout to each server your code, and after that make a script svn_up.sh like this:

ssh  server_one_ip_address svn up /path_to_working_copy_on_server1
ssh  server_two_ip_address svn up /path_to_working_copy_on_server2

Use sh svn_up.sh instead of svn up

Same working copy of the code with 2 SVN servers

6 Answers6

Linked