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

Re: general svn question for large env

From: Rachael Russell <rachael.russell_at_gmail.com>
Date: 2005-08-11 14:09:38 CEST


The way I've always worked in a dev environment:

1. Developers check out relevant working copy of trunk (or branch where
necessary) onto local PC -- if using windows, then tortiseSVN or a
plugin for your dev environment makes this a bit easier...
        svn co repositoryname workingfolder
2. Changes are checked in against trunk/branch, then tagged as a dev
build (and any merges done if required)
        svn copy trunk/branchpath tagpath
3. Tagged Dev build is exported (or checked out) onto dev box for dev test
        svn export devtagpath dir
4. Tag ready for test is then exported or checked out to stage box
        svn export testtagpath dir
5. On passing test, build is retagged as a production build number
        svn copy testtagpath stagetagpath
        svn export stagetagpath dir
6. Production version is checked out or exported onto production box (if
prod servers are able to access your repository - otherwise just copy it
from the staging server using whatever method - FTP, scp, rsync etc)
        svn copy stagetagpath prodtagpath
        svn export prodtagpath dir

Dev/stage versions of tags can then be removed if required to save
space. Of course, if changes are made, the process should be repeated
(to make sure you dont miss any testing stages).

Hope that helps! Would be good to know how others do this also... we
also mix in ant builds at each stage to enable deployment of our java
apps to the application servers, but other environments may not require


Steve Rieger wrote:

> hi all
> i have the following set up and am looking for pointers.
> all the developers write on their local boxes, then upload to the dev
> server
> QA upon request from dev moves from dev to stag
> once it passes QA sys admin moves from stag to prod.
> i am sure that there is a way we can do all these changes through
> svn, how would i go about doing this.
> does anybody have any docs or pointers.
> thanx
> --
> Steve Rieger
> AIM chozrim
> ICQ 53956607
> Cell 646 335 8915
> steve.rieger@tbwachiat.com
> This e-mail is intended only for the named person or entity to which
> it is addressed and contains valuable business information that is
> privileged, confidential and/or otherwise protected from disclosure.
> Dissemination, distribution or copying of this e-mail or the
> information herein by anyone other than the intended recipient, or an
> employee or agent responsible for delivering the message to the
> intended recipient, is strictly prohibited. All contents are the
> copyright property of TBWA\Chiat\Day, its agencies or a client of such
> agencies. If you are not the intended recipient, you are nevertheless
> bound to respect the worldwide legal rights of TBWA\Chiat\Day, its
> agencies and its clients. We require that unintended recipients
> delete the e-mail and destroy all electronic copies in their system,
> retaining no copies in any media. If you have received this e-mail in
> error, please immediately notify us via e-mail to
> disclaimer@tbwachiat.com. We appreciate your cooperation.
> We make no warranties as to the accuracy or completeness of this
> e-mail and accept no liability for its content or use. Any opinions
> expressed in this e-mail are those of the author and do not
> necessarily reflect the opinions of TBWA\Chiat\Day or any of its
> agencies or affiliates.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 11 14:11:37 2005

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.