Web hook push events not working

When I click TEST HOOK, Web hook is working, url received the data.

Started GET "/xxx/xxx/hooks/36/test" for xx.xx.xx.71 at 2015-10-22 11:12:36 +0800
Processing by Projects::HooksController#test as HTML
  Parameters: {"namespace_id"=>"xxx", "project_id"=>"xxx", "id"=>"36"}

When I push code to the repository, Web hook url didn't receive any data.

Started POST "//api/v3/internal/allowed" for 127.0.0.1 at 2015-10-22 11:02:23 +0800
Started POST "//api/v3/internal/allowed" for 127.0.0.1 at 2015-10-22 11:02:24 +0800
Started GET "//api/v3/internal/broadcast_message" for 127.0.0.1 at 2015-10-22 11:02:25 +0800
-end-

---

System information
System:		Ubuntu 14.04
Current User:	git
Using RVM:	no
Ruby Version:	2.1.2p95
Gem Version:	2.2.2
Bundler Version:1.10.6
Rake Version:	10.4.2
Sidekiq Version:3.3.0

GitLab information
Version:	8.1.0.rc2
Revision:	62f6e84
Directory:	/home/git/gitlab
DB Adapter:	postgresql
URL:		http://git.xx.com
HTTP Clone URL:	http://git.xx.com/some-group/some-project.git
SSH Clone URL:	git@git.xx.com:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	no

GitLab Shell
Version:	2.6.5
Repositories:	/home/git/repositories/
Hooks:		/home/git/gitlab-shell/hooks/
Git:		/usr/bin/git

Title changed from webhook push event not working to Web hook push events not working

This is happening for us as well. Web hook push events are triggering but not always. Seems to be quite random.

We are using the community edition of Gitlab

Can someone confirm, will the push-event be triggered for master branch, when I do merge a "develop" branch to "master" in the following way?

git checkout master
git pull origin/master
git checkout develop
git pull origin/develop
git rebase origin/master
git push origin develop -f  #===>CMD[1]
git checkout master
git merge origin/develop
git push origin master  #===>CMD[2]

Will the push-event be triggered at both CMD#[1] & CMD#[2], or just CMD#[1] or CMD#[2]?

I noticed push-event didn't get triggered on CMD#[2]. Not sure of the logic behind the push-event.

---

We are on GitLab Community Edition 8.1.4 295b1f0

Happened for me as well on gitlab.com about three days ago. The following commit didn't trigger a webhook, manually doing a test trigger did: https://gitlab.com/protogrid/landing/commit/940ba8f06b3c41e953f7128654c00dcec7b8b246 ; Note: Private repo.

We also experienced the following, probably related behaviour with that commit: https://gitlab.com/gitlab-org/gitlab-ce/issues/853

I am experiencing this too, running GitLab Community Edition 8.8.5. Webhooks works, but not always. It's quite random as @shyam1 mentioned earlier.

mentioned in issue #14449 (moved)

mentioned in issue #18960 (moved)

Added webhooks label

We're seeing this issue on 8.11.2. Sometimes we get a timeout error from the ProjectWebHookWorker (which could be explained by load or network issues) but sometimes we just see nothing at all in the sidekiq logs.

Is there anywhere we can look to debug this better? Or any debug logging we can enable?

Happening for me too on gitlab.com - manual test button always works, git push mostly doesn't.

Same here, gitlab.com is not sending anything unless I manually use the test button.

Can confirm, TEST button and other events (wiki page, merge request, etc) work, only commits do not. GitLab 9.1.0 on ARCH.

Hmmm, this was opened a year ago and looks like that there is no fix yet :). I have same problem with Gitlab CE 9.1. Test button works nicely but i havent seen push trigger to work so far (only few push requests so far).

Is there any plan to check this problem out?

Thanks for any help

Just a reminder, seeing as this is still broken after a year and a half...

GitLab are more likely to notice it if we click the above (under the OP).

And ask your coworkers/etc to click it too.

Can anybody confirm this bus is still up on the latest stable version of GitLab, please?

Seems like it's been better for us the last month or so.

@fraserredmond

Seems like it's been better for us the last month or so.

What do you mean by better? Does it work now or not?

Sorry for being vague :-)

Just asked my colleague that it affected, he said it always works now.

(But how long it's been working... that's still vague, could be anything between 2 weeks to 2 months.)

@fraserredmond

Okay, thank you for the clarification!

I'm closing this issue now.

closed

didn't had this problem for couple of months and not it has started happening again since the new update ? Is there any plan of fixing this any soon ?

Seeing the same problem with GitLab CE 9.3.3. A webhook test works fine and sends JSON data to the server, however, received pushes call the server with a POST request, but there is no JSON data.

@fraserredmond this seems to be working for you. Can you tell me which version of GitLab you're using? Thanks!

we're using the free public version of Gitlab. The push events seem to work sometimes, but not all the time. I can't find any good pattern.

Best regards,

Craig.

I have the same issue. I have configured a webhook and a Jenkins CI integration. For both test button works perfectly, but the "Push event" has never worked. Does anyone be able to fix that

Repo: private

Platform: Community Edition (CE) (Cloud)

PD: I have also made a requestb.in log and it stills without any access.

FWIW, I tested against a 9.5.5 CE docker image and found it to be good.

I have finally received them all ( may be some issue with the GitLab web hooks queue). Now just re-tested and it has worked has expected. Thanks!

mentioned in issue gitlab#5217

mentioned in merge request !14785