git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacob Helwig <jacob.helwig@gmail.com>
To: Jeremiah Foster <jeremiah.foster@pelagicore.com>
Cc: git@vger.kernel.org
Subject: Re: Unable to coax hooks into working
Date: Mon, 26 Apr 2010 11:11:15 -0700	[thread overview]
Message-ID: <v2u8c9a061004261111l429b0c8cs73cf7e1afea3d39f@mail.gmail.com> (raw)
In-Reply-To: <B65E8227-B3C0-4AB8-A225-4A5661523CAD@pelagicore.com>

On Mon, Apr 26, 2010 at 11:04, Jeremiah Foster
<jeremiah.foster@pelagicore.com> wrote:
>
>
>>>      We're using debian testing and git 1.7.0.2 with the http-smart backend.
>>>
>>>      What should I do to get hooks working?
>>
>> Use the right hook.
>>
> I followed that document I listed explicitly. After lining up the right command, the right hook, and the right location, including correct executable bits as well as script ownership, a functioning script was built. Yet when the corresponding git command was called, the command failed to send data to the client which leads me to believe that the hooks wasn't called.
>
> Here is so more information on the http backend I was referring to: progit.org/2010/03/04/smart-http.html
> And the manual page: www.kernel.org/pub/software/scm/git/docs/git-http-backend.html
>
> Can I confirm that hooks work with this type of transport?
>
> Jeremiah
>

The real problem is that you're using a post-commit hook (or at least
everything you said in your original email implies you are).
post-commit hooks are only triggered in your _local_ repository, since
this is the only place you actually commit.  Doesn't matter which
transport you're using, post-commit will never be triggered by a push.

You want one of the receive, or update hooks, if you're putting this
in a central place, where it needs to be triggered by someone doing a
push in to the repo.

  reply	other threads:[~2010-04-26 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 18:04 Unable to coax hooks into working Jeremiah Foster
2010-04-26 18:11 ` Jacob Helwig [this message]
2010-04-27  8:33   ` Jeremiah Foster
2010-04-27  8:52     ` Michael J Gruber
2010-04-27  9:08       ` Jeremiah Foster
2010-04-27 10:47         ` Michael J Gruber
  -- strict thread matches above, loose matches on Subject: below --
2010-04-26 12:32 Jeremiah Foster
2010-04-26 12:55 ` Michael J Gruber
2010-04-26 17:59   ` Jeremiah Foster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v2u8c9a061004261111l429b0c8cs73cf7e1afea3d39f@mail.gmail.com \
    --to=jacob.helwig@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jeremiah.foster@pelagicore.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).