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.
shouldn't run anything time-consuming in the post-commit hook. And
certainly nothing that generally can't run multiple times concurrently
(such as builds).
I would probably do in your case is implement a continuous integration
tool, and use it to detect and execute these post actions on a commit.
That way, if there is a flurry of activity, the
setup will handle the post work
elegantly and correctly. I would do this at the very least for your builds.
Quicker things (commit emails) are perfectly appropriate for post-commit.
Hope this helps,
Subversion Training & Consulting Services | ttp://
Download Eclipse bundled with Subversive today! |
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-07 15:26:54 CEST