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

RE: Subversion and Project Environments (Dev / Test / Prod)

From: Ian Leader <ian.leader_at_line.co.uk>
Date: 2004-05-27 02:38:54 CEST

We are using Subversion to manage website development (actually e-learning, but it comes down to more or less the same thing).
Are current process is the following:
- All developers/designers etc check out and work on their own working copy, in the normal way
- Once we want to make a release to QA, we make a tag for the release, usually called YYY_MM_DD_n
- Then, we do an export, and ZIP it up. We do this rather than a check out so there are no .svn folders in the releases, and so that people are not tempted to/do not accidentally make changes directly on the release.
- Finally, we FTP the ZIP files to the QA server and unzip to test (or we upload the ZIP file into a learning management system depending on exactly what we're doing).
- When we do a production release, we follow the same steps, usually sending the ZIP to the client.
Although this process works, it starts to fall down unless you keep a complete copy of your website in the final directory structure in Subversion. We have various bits of common JavaScript code, and a few things that need to be compiled, and at the moment this involves manual copying, which is tedious and potentially error-prone. To get around this we're starting to implement a build system (we'll probably use Apache Ant) which will allows us to pull together a complete build from various folders into the final structure, compile things that need compiling, then ZIP everything up, create manifest files, etc. at the push of a button (or from a command line anyway).
I hope this is helpful.
Best regards,

        -----Original Message-----
        From: Brendan van Drempt [mailto:Brendan_vanDrempt@scholastic.com.au]
        Sent: Thu 27/05/2004 01:27
        To: users@subversion.tigris.org
        Subject: Subversion and Project Environments (Dev / Test / Prod)

        I am in the processing of setting up Subversion to manage the development of
        a website.
        Subversion Repository on Windows Server machine running SVNserve. Windows
        development machines running TortoiseSVN client. (soon to add mac
        development machines, when we decide on a suitable mac subversion client)
        * What is the best way to implement Subversion across my Dev / Test /
        Production sites?
        * Should each environment be a 'working copy' of the repository, and then
        use a client tool to update to particular revisions? (in addition to the
        working copies of the developers)
        * Should I be using 'tags' to set releases?
        Need a bit of clarity here.
        Brendan van Drempt
        Analyst / Programmer
        Email: brendan_vandrempt@scholastic.com.au
        To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
        For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 27 02:42:37 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.