[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Source migration

From: McDonnell, David <dmcdonnell_at_csu.edu.au>
Date: 2003-08-22 03:34:23 CEST

Hi all,
 
We're looking at implementing a source control system in my
organisation, and subversion is looking like an excellent candidate. The
one wall I have hit is in relation to source migration. We have 3
seperate environments: devel, qa and production. Our current in-house
written system is a source versioning system as well as a migration
utility (eg a developer can migrate a file to qa or production from the
command line).
 
I know subversion does not do this automatically, but it looks like this
could be implemented on top of the system. I was envisaging a project
layout like this:
    /project/trunk/
        -> main development line
    /project/migration/
                /qa/ - qa branch that is checked out to qa enviroment
                /prod/ - prod branch checked out to production

And to migrate a file you would just "svn copy" it from /project/trunk
to /project/migration/qa/ or /project/migration/prod/ depending on where
you wanted to migrate it to. To achieve this a "svn checkout" process
would need to run regularly on each box to get the latest version of its
migration branch (prod or qa).

Now before I reinvent the wheel, :) does anyone have any experience they
would like to share on migration? Has anyone used subversion to do this,
or used something else with subversion to get the same result?

Cheers,
Dave
 
======================
Dave McDonnell
WWW Programmer
Online Services
+61 2 69334217
david.mcdonnell@csu.edu.au
======================

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 22 03:36:14 2003

This is an archived mail posted to the Subversion Users mailing list.