Re: SVN and Cruise Control with Multiple Evironments/Revisions

> Does anyone have any better ideas on addressing this problem?

Automate the checkout, CI-setup, and deployment so it's possible to set up
CI builds on an arbitrary source-control URL on a whim. That way, you can
press a button and have a new build set up for production code, but in the
dev environment, and promote changes as normal (albeit in a higher priority
manner).

Make sure your merges are done often, and are smaller. Merge-difficulty
increases very quickly the longer it is delayed.

---------------------------------------------------------------------
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 13:15:22 CEST