Barry Roberts wrote:
> The trick is, I would like to be able to use hook scripts to
> automatically check out a copy to the production directory once it's
> been tested and proven on the test servers. I'm not sure how to do
> that. Is it possible to use a hook script to look for a particalur
> tag/branch/copy and know that it means it's production ready? I can't
> tell if this is possible from reading the documentation.
We're basically doing something like this currently with CVSNT and I'd recommend
_against_ automating the production checkout. We are using a POSTCOMMIT hook to
keep the test server in sync with the repository. Major rewrites happen on
branches and minor tweaks happen on the trunk. The production server is always
on the trunk, but the test server can be on a branch. It all works really well
and we'll be following the same scheme when we move to Subversion.
The reason we manually force a production update is for consistency. The
production server should always be handled manually (IMHO), so that there is an
official "release" when it is updated. There are occasions when something that
works fine on the test server will not work on the production server (forgot to
update the include files, for example). Rather than having the production
server update automatically, the developer has to manually trigger the update,
and then can more easily remember to immediately test the changes.
You have to also think about any time you have to revert the production server.
If you are based on an automatic trigger of some sort, do you delete the
tag/branch? And then what happens? How does the server trigger know which
version to revert to? I think it is better to keep the production site a manual
My 2 cents
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Lanham, MD 20706
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Oct 16 15:45:08 2003