On 4/29/2010 1:06 PM, Dan Stromberg wrote:
I'm working on some Subversion-related software for propagating trunk
checkins to any of dozens of target branches, based on trunk's checkin
comments (that is, where the checkins need to subsequently go automatically is
determined by the checkin comments in trunk, and those comments are
prepared pretty consistently by a custom GUI; the GUI piece is already
written and in production).
I of course want it to work well when we deploy it - and the trunk
we'll ultimately be running it against is rather huge.
So to make it work well from the start, I need to test it well. To
test it, I really want to copy from one SVN server's trunk to another
SVN server's repository - flattening a significant part of the early
history from the source trunk, and then having as-identical-as-practical
checkin comments for the later history.
I don't understand the need to flatten the trunk. Fanning out from the
trunk to many branches should be straightforward enough, fhough.
Is there already a way of setting up such a test branch? I've googled
about it quite a bit and come up with things that are close (svnsync:
way too much test data, svn merge: too few checkin comments unless I
do them individually somehow), but not quite what I need. It's
seeming like writing the program to prepare the test environment is
nearly as complex as what I'm intending to test.
Please note that although I've been an SVN admin in the past, I do not
have administrative access to these SVN servers.
The only way you can modify existing history is with a svnadmin
dump/filter/load and you need admin access for that. Can you svnsync
the live repo to one you control, then dump from there to get a base for
your test?
--
Les Mikesell
lesmikes...@gmail.com
