svn hook concurrency

[Andreas Zitzelsberger <sv...@az82.de>]

Hi,

does subversion take care of concurrency of hook skripts (especially 
post-commit) / what happens if a new transaction is commited before the 
post-commit hook skript of the previous transaction is completed?

Background: I'm currently working on a multi-system web site compiling / 
publishing system. I want to use subversions post-commit hook to keep a copy 
of the head revision up-to-date and to invoke the compiler.

Thanks a lot,

Andreas 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn hook concurrency

[Andreas Zitzelsberger <sv...@az82.de>]

> Well, only if you intend to have repositories on multiple
> platforms... The post-commit hook (like all other hooks) runs on the
> Subversion server, not on the clients. So you really only need to
> code it to work on whatever architecture is hosting your repository.
The whole thing is server-side only. I wanted to support any platform where 
Python is available, but I think I'll stick to Posix - compatible systems.

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn hook concurrency

[Ryan Schmidt <su...@ryandesign.com>]

>> On Oct 17, 2005, at 23:10, Andreas Zitzelsberger wrote:
>>
>>> does subversion take care of concurrency of hook skripts (especially
>>> post-commit) / what happens if a new transaction is commited  
>>> before the
>>> post-commit hook skript of the previous transaction is completed?
>>>
>>> Background: I'm currently working on a multi-system web site  
>>> compiling /
>>> publishing system. I want to use subversions post-commit hook to  
>>> keep a copy
>>> of the head revision up-to-date and to invoke the compiler.
>>
>> I don't know the answer to your question, but I can recommend that
>> you defer updating the working copy and invoking the compiler until
>> after the post-commit hook has finished running. The Subversion
>> client will not return control to the user until the post-commit hook
>> has exited, so you want to keep it as short as possible.
>
> Thanks. That means my compiler will anyway need some sort of platform
> independent process communication :(


Well, only if you intend to have repositories on multiple  
platforms... The post-commit hook (like all other hooks) runs on the  
Subversion server, not on the clients. So you really only need to  
code it to work on whatever architecture is hosting your repository.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn hook concurrency

[Ryan Schmidt <su...@ryandesign.com>]

On Oct 17, 2005, at 23:10, Andreas Zitzelsberger wrote:

> does subversion take care of concurrency of hook skripts (especially
> post-commit) / what happens if a new transaction is commited before  
> the
> post-commit hook skript of the previous transaction is completed?
>
> Background: I'm currently working on a multi-system web site  
> compiling /
> publishing system. I want to use subversions post-commit hook to  
> keep a copy
> of the head revision up-to-date and to invoke the compiler.

I don't know the answer to your question, but I can recommend that  
you defer updating the working copy and invoking the compiler until  
after the post-commit hook has finished running. The Subversion  
client will not return control to the user until the post-commit hook  
has exited, so you want to keep it as short as possible.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org