For now I'm trying to do the following:
access-hook.bash has:
delayed-notify.bash $@
delayed-notify.bash has:
sleep 10
...
curl ...
I'm expecting access-hook to spawn new process and return without
waiting for it to finish to let the service to do its job. But when i
do push - it
On Thu, Sep 12, 2013 at 3:15 PM, Junio C Hamano gits...@pobox.com wrote:
Eugene Sajine eugu...@gmail.com writes:
Is it possible to have access-hook to be executed after receive?
The whole point of access-hook is to allow it to decide whether the
access is allowed or not, so that is a
Eugene Sajine eugu...@gmail.com writes:
So are you really sure that it is a non-starter to have
--before-service/--after-service options for access-hook?
Given the definition of --access-hook in git help daemon:
--access-hook=path::
Every time a client connects, first run an
Junio,
Thanks for the clarification! Your solution does look better.
For now though i think i will have to delay the notification somehow
and let the service finish first then notify the server.
Thanks again!
Eugene
On Thu, Sep 12, 2013 at 5:08 PM, Junio C Hamano gits...@pobox.com wrote:
On Thu, Sep 12, 2013 at 5:16 PM, Eugene Sajine eugu...@gmail.com wrote:
Junio,
Thanks for the clarification! Your solution does look better.
For now though i think i will have to delay the notification somehow
and let the service finish first then notify the server.
Thanks again!
Eugene
Junio C Hamano gits...@pobox.com writes:
Eugene Sajine eugu...@gmail.com writes:
So are you really sure that it is a non-starter to have
--before-service/--after-service options for access-hook?
Given the definition of --access-hook in git help daemon:
--access-hook=path::
On Thu, Sep 12, 2013 at 6:20 PM, Junio C Hamano gits...@pobox.com wrote:
Junio C Hamano gits...@pobox.com writes:
Eugene Sajine eugu...@gmail.com writes:
So are you really sure that it is a non-starter to have
--before-service/--after-service options for access-hook?
Given the definition
Eugene Sajine eugu...@gmail.com writes:
So even if we feed the exit status of the service process to the
hook script specified by the --post-service-hook, it does not tell
the script if the service succeeded in that sense.
I see what you're saying.
In my particular use case I can work
8 matches
Mail list logo