The approach I ended up taking was freezing commits to the stable branch before and during a deploy. The stable branch is the only line of code we deploy -- the trunk is where active development takes place. With the codebase frozen, we can be sure nothing sneaks into the stable branch while the tests and the deployment are running, and consequently that nothing unexpected makes its way into production.
Thanks! Cody --- Cody Robbins Sakuzaku, LLC wearesakuzaku.com > This seems like a very common problem, i got 2 environment Stage and > Production, the code get deployed to Stage, gets tested and if > everything goes well gets deployed to Production. > > Now the problem is i want to deploy the exact code that got on Stage, > to Production, not the latest one, as there have been code changes > while testing Stage. > > Is it possible to to deploy the code of certain revision (not latest) > or labeled code using Capistrano ? > > Thanks ! --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
