Quoth Magnus Andersen <mailto:mag.andersen@gmail.com>:
> My initial thought was to create tags for testing and
> production and when the files/directories were tagged I have
> another post-commit script that pushes the files to the test
> or production servers.
>
> My problem is that I only want to move one directory,
> sometimes only one file, to test/production, not the entire trunk.
Subversion uses "cheap" copies, so it doesn't cost any more storage on
the server to copy the entire trunk to a branch/tag vs. a single file.
Which is why most people just copy the whole trunk, since it's simpler.
But there's nothing stopping you copying just a single folder or even a
single file to the branch/tag -- but unless you're consistent, then
you'll have to write a more complicated script (since the input it's
dealing with could be entirely different each time). You can also
switch a working copy over to an existing tag/branch, make changes, and
then commit against that (although it's considered "bad style" to do
that for tags, since they're supposed to represent fixed snapshots).
What are you actually trying to reduce? If you're trying to reduce the
amount of data you have to send to test/production, then you could try
sending it via rsync or diff/patch, so they only get the minimal set of
changes rather than duplicating everything.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 28 03:05:56 2006