[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS question...
From: Ken Keefe <kjkeefe@gmail.com>
> I know this isn't a CVS list or a PHP list,
Actually, I consider version control a greatly underappreciated aspect
of any system or even user document administration.
> Anyway, what do other people use for this problem?
The whole purpose of a centralized version control repository is
to cut down on the manual processes. Checkouts should be done
on the relevant tag for the relevant environment. E.g., HEAD for
development, another tag for test, another tag for release.
So while you're doing check-ins/check-outs on HEAD or some fork
in development, you should be automating a checkout to a test
server for inspection, and another automated checkout to your
production server for actual deployment.
CVS is designed to work over SSH shell access.
If you don't have shell access on the test and/or production
servers, then do a checkout on its behalf to a local working
directory, and then rsync the changes over to production.
You can exclude the CVS files in your rsync if you wish.
--
Bryan J. Smith mailto:b.j.smith@ieee.org
-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.