Re: svn commit still holds locks when server-side post-commit runs

Markus Kuhn wrote:
> We use Subversion to give users version-controlled write access to a web
> site. The web server serves HTML files from a directory that is a normal
> svn working directory. Users check out their own working copy, and when
> they commit their changes, we use a post-commit script to run "svn
> update" on the web server's working directory, such that the commited
> changes become visible to the world wide web. This has worked extremely
> well for almost two years now.

Been there, done that, wrote some modules to make it easier:

        http://search.cpan.org/search?query=SVN::Notify::Mirror
        http://search.cpan.org/search?query=SVN::Notify::Config

I alway run a test server that mirrors trunk and only push things to the
production server when a tag (matching a specific regex) is created (see
  the docs for SVN::Notify::Mirror on how trivial this is to configure).

It's considered bad form to be editing your live site except during
extraordinary circumstances (e.g. serious failures)... ;-)

John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-04 19:29:54 CEST