Geek Answers Handbook

Saving code on multiple SVN servers

As an independent developer, I like to support all my developments on my own SVN server, both for continuous integration and for accounting regarding what changes were made and when.

Now I am working with a client who also uses SVN internally and, obviously, would like me to work with my development team on my SVN server.

This is great overall, but it would also make me abandon my practice of working on this project and lose my internal accounting method. If this happens a lot, then I will have fairly free working standards - ultimately, they will change according to the project (which I obviously do not want).

Is there any creative way to get the best of both worlds, and is there code to commit on both SVN servers? I don't mind a bit of extra work either in front or on each commit / update to disable it.

svnsync looks like a good option. Has anyone tried this? Does anyone have any other suggestions?

+5
source share
6 answers

I am not sure what the problem is. You are using a different SVN URL, but everything else is the same. What do you mean by “book storage”?

Perhaps this comes down to who owns the code - if it is them, they have every right to ask you to use their version control system. And, since it sounds like you are working with a development team, they are superior to you.

, , , , , , , ..

( , ), , , , , , .

+2

(?) svndump , .

, , - , .

+1

: , , , . , svn commit hooks - i.e , , . script , .

, , , .

+1

, . , , . , .

0

, Subversion ( , , ...), Java, Subversion . .

Subversion, SvnKit.

0

. "", , , , , .., . , , svn:external , , .

, , , . , . ( ), , .

git Subversion

git Subversion. .

0

More articles:


All Articles