Moving from one svn server to another, despite heavy use of absolute external references?

We have 3 subversion repositories on a single subversion server, and
we want to move them to a new subversion server.

This seems simple enough - until you start to consider all the
absolute external references (in branches and tags) we'd want to think
about updating - and we're a little skittish about updating our tags.

I calculated that for one of the 3 repos, if we have an automatic
process that takes about a half hour to update one branch or tag, it'd
take about 9 days of continuous updating to adjust all of our
externals. That's kind of a long time, and I'm afraid the estimate is
more likely low than high.

There's also the option of generating a list of all the hostnames and
IP's used in our external references and stealing those hostnames
and/or IP's, so that the externals don't need to be updated.

Has someone else already been down this road?

I have a tool that does a reasonable job of updating external
references by piping them all through sed, but it's never been used on
this scale. If there's something in common use, I'd probably use that
instead. Is there something like this available?'

What are best practices on this sort of scenario?

(No, I wouldn't have architected it this way at all, but I'm afraid
we're stuck with it. I'd've used ant/make variables or environment
variables instead, and failing that symlinks instead, and failing that
relative external references, and failing that a DNS CNAME, or at
absolute worst a series of _hosts_ files for the Subversion server)

Thanks!

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2376395

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-28 22:57:53 CEST