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

SVN and Cruise Control with Multiple Evironments/Revisions

From: Chandu <chandra.vedantham_at_gmail.com>
Date: Mon, 28 Apr 2008 13:57:03 -0700 (PDT)

Hi,
We have three different environments Dev/Testing/Prod.
Currently we are having problems with the production deployment
process.
Our team works on multiple requests that come in and sometimes the
requests might need the team to work on same file.
The problem is if one of the request is complete and tested in testing
environment and is ready for Production move, the same set of files
might contain the code changes which are not complete yet and are not
ready for production move.
Currently we are maintaining a seprate branch for the Prod
environment, merging the changes to the branch and then using Cruise
Control to deploy the code. But the merging has become a painful
process.

Does anyone have any better ideas on addressing this problem?
-
Chandu

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-04-29 07:08:53 CEST

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

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