RE: Slow post-commits causing long time to commit on user's side.

From: Jan Du Toit [mailto:jan.du.toit_at_gmail.com]
Sent: Friday, August 07, 2009 2:11 PM
To: users_at_subversion.tigris.org
Subject: Slow post-commits causing long time to commit on user's side.

Hi,

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 minute).

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,
right?

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.

---
Windows servers are difficult to run apps in background mode for,
(unlike*nix where you just append a &!)
What I do then is to have my post-commit hook write the file or
directory paths to a file, and I regularly read that in a scheduled job
and apply various tasks to it.
 
Alternatively, write your hook scripts in perl, and let them fork
themselves into the background. Even on Windows:
http://www.perlmonks.org/?node_id=663081
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2381315
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].