You shouldn't do anything in a post-commit hook that will take a long time.
Maybe a quick email to a concerned party that a particular file was updated,
but that's it. It sounds like you're building a continuous build system via
your post-commit hook. However, there are plenty of continuous build systems
that will handle everything you want to handle in your post-commit hook and
more. As a bonus, they run in parallel of Subversion, so you don't have to
wait for these systems to complete their task.
Take a look at Hudson <https://hudson.dev.java.net/>. It'll handle
everything you're probably doing with your post-commit hook.
On Fri, Aug 7, 2009 at 9:11 AM, Jan Du Toit <jan.du.toit_at_gmail.com> wrote:
> I have a question with regards to svn post hooks:
> I have implemented a post-commit hook for our repository. The post-commit
> performs a lot of things (mailing, building, synching with a legacy flat
> file system, etc) the result is that the post-commit is rather slow (+- a
> The problem I'm having is that when the user commits the commit does not
> return until the post-commit has also been executed. Thus the user waits a
> very long time for the commit to go through.
> Semantically the post-commit is not part of the user's commit, i.o.w the
> user should not even be aware of the post-commit - its just something
> (additionally) happening on the server's side as a result of a commit,
> How can I get the post-commit to be forked/threaded or something so that
> the user making the commit does not have to wait until the post-commit has
> also executed?
> Maybe this is rather a topic with the SVN client? We are using TortoiseSVN.
> We are running SVN 1.5.5 on a Windows Server 2003 R2 SP2.
> Thanks in advance.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-07 18:11:51 CEST