Re: update hook per project (or directory)

On 3/2/07 at 9:42 AM, jan.hendrik@myrealbox.com (Jan Hendrik) wrote:

> Concerning Re: update hook per project (or dir
> Andrew Brosnan wrote on 1 Mar 2007, 13:18, at least in part:
>
> > The idea is to update the wc running a website, so only that one wc
> > will auto-update. I was trying to avoid running svn up on the entire
> > wc. when perhaps only a few files had been committed.
> >
> > Funnily enough, I started writing a script to do this using svnlook
> > just as I got your response. Thanks Andy!
>
> But consider what happens to your website if the svn update
> execution fails for any reason

the script needs to deal with that, i.e. - logging, error handling

> or if there is another commit while
> the script still runs

...hmmm, I don't know. The script just runs svn up. What happens if one
user commits while another is running update? That should be OK.

> Guess this will be less of an
> issue if repository and the website wc are on the same machine,

one is, a mirror is not

> but if they are not and you have to run the script through ssh/telnet
> you might more easily end up with a wc lacking some updates.

Not sure how. An update occurs after any commit. Seems like it should be
OK.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 2 13:38:08 2007