On Feb 2, 2008 1:01 PM, Will Sargent <[EMAIL PROTECTED]> wrote: > My question is: does cc.rb have any way to manage this internally? Or > is the best way to handle this by using svn switch on the backend?
If you create a separate project with the branch URL, and give it an appropriate name (different than the trunk project), this should work fine. The only problems we've had is when some of our deploy task tests did a switch on the working copy - but if you don't do that, it should stay pointed to whatever branch URL you originally created with. So, bottom line, a separate project per branch. Reply to this thread if that doesn't work... -- Chad _______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
