On 2/22/06, Phillip Susi <psusi@cfl.rr.com> wrote:
> Philip Hallstrom wrote:
> > Hmmm. If I read what you're saying right, you mean setup a post-commit
> > hook (or whatever it's called) to automatically check out any commits
> > made to the vhost, right? The problem I see with that is the designers
>
> You could do that, or have a cron job do an svn update every 5 mins or
> something.
Both of these could get tricky if you don't take proper precautions.
The post-commit hook will block the client while the checkout/export
on the server completes. If you just have the hook spawn a new
process for this, you run the risk of trying to do more than one at
the same time. The cron job could have similar issues.
These can be worked around/mitigated, but you need to be conscious of
them before putting it in production. A continuous integration server
like CruiseControl, or a build management server like Anthill, may be
a help here.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 23 02:31:59 2006