Keeping code in multiple SVN servers

Question

As a freelance developer, I like to keep all my development in my own SVN server both for continuous integration as well as book-keeping as to what changes were made and when.

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

This is great in general, but it would also cause me to abandon my working practices on this project and lose my internal book-keeping method. If this happens alot, then I'll end up with pretty loose working standards - ultimately varying by the project (which I obviously don't want).

Is there some creative way to get the best of both worlds, and have the code exist on commit in both SVN servers? I don't mind a little extra work either up front or on each commit/update to pull it off.

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

Answer 1

I am not sure what the problem is. You use a different SVN URL, but everything else is the same. What do you mean by "book-keeping"?

Perhaps it boils 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 have you outnumbered.

Because there are other developers involved, you obviously must work off their repository to make sure you always have the latest code and thus avoid conflicts, etc.

If you are concerned about keeping a copy of the code (assuming that is legal), there are many ways to achieve that, e.g., periodically export the working folder pointing to their server to another working folder on your machine pointing to your server, and commit.