Re: Question

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Lancisi <address@hidden> writes:

> We have an offsite lab that currently pulls test suites from our cvs
> repository at our home office while running tests.. Problem is, the
> test suites in cvs are huge and will sometimes take hours to checkout
> over the dedicated pipe (vs a couple minutes when checked out at the
> home office).
> 
> In order to speed things up, I'd like to set up a cvs read only mirror
> copy of the repository at the offsite that stays up to date
> automatically with the master repository. That way the offsite lab can
> checkout test suites without having to go through the pipe.
> 
> My question is, does cvs support the notion of  a read only mirror repo? 

Sure. The various *BSD folks have been doing this for years.

The easiest way is to setup a CVSupd daemon on the primary server and
run CVSup from a crontab or on demand on the mirror.
(See http://www.cvsup.org/)

(Note: Some folks have setup e-mail triggers to cause CVSup to be queued
when a particular e-mail address <foo> gets e-mail (via .procmailrc
filters I believe) and ensure that the <foo> list is on an e-mail
distribution list for every commit to the master repository.)

You may also want to add something to your commitinfo trigger to verify
that you are only doing commits to the primary repository.

This is not 100% necessary if you are careful to use something like the
CVS_LOCAL_BRANCH_NUM feature introduced in cvs 1.12.x. 

To do commits to the primary repository out of a tree checked out of the
secondary, users would need to use the command-line '-d
:ext:primary-repository.host.name:/repository/path' argument to CVS
instead of just using the CVS/Root default values.

If you are a pserver shop and looking for a commercial answer, then use
of something like the wandisco.com 'CVS Replicator' may be the right
choice for you.

        Good luck,
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFCTGAl3x41pRYZE/gRAjI7AKC9qnWybsw4vNJdgfC+rOsXAOrDHQCgmzgE
Ax03mGQ1N8zFp0aqd1c7e7c=
=yjEm
-----END PGP SIGNATURE-----