> On Fri, Jan 6, 2012 at 14:16, fmdano <fmd...@gmail.com> wrote: > > Hey all, > > right now I am thinking about using a post-commit hook script to > > update my dev server when a developer checks in changes. > > I want to know how the test server could be updated from svn after > > some testing has been done and a tag of a release has been created? > > Would the best way to update the test server from a tag be to export > > the tag into the existing test server folder and over write the code > > in there, and hot have the test server be a checked out copy, or can > > you use a tag to update the test server if it is a checked out working > > copy? > > > > any ideas about how to do this would be greatly appreciated. > > Usually this is done via a Continuous Integration server like CruiseControl, > Jenkins, TeamCity, etc. They'll check out your code, run whatever build > scripts > & tests you define, deploy (if you have a script/command for it to run), and > create a tag (usually you only do this on success). You can also configure > them > to send email/RSS/twitter/SMS/whatever notifications on various events, and > usually get a web dashboard to monitor the status of your environment.
Agreed. This is the way to go. Even though you could do it as a post commit hook. You have much more flexibility with build scripts and cc servers and you can run them on a separate machine so stuff scales better. BOb
