Geek Answers Handbook

How can I debug Gitlab web hooks?

I am currently using gitlab_6.9.1-omnibus-1_amd64 on a new Ubuntu 12.04 installation in a KVM instance with dedicated WAN IP.
Everything works except for web hooks. I have added all the possible ways to add a web hook.

  • Gitlab shows hooks with a test button that does nothing.
  • I also added global interceptors via gitlab-rake, but that does nothing.
  • Sidekiq is working.
  • And nothing in sidekiq log, like gitlab-ctl - tail , shows nothing.

# gitlab-rake gitlab:web_hook:list

Could you show me how I can debug web hooks on GitLab?

PS: I would like to ask about this on the Fault server, but I thought that it should be here, since this will be debugging help.

+7
gitlab sidekiq webhooks
source share
1 answer

First, make sure your server can access the Internet or a WebHook address, for example. use curl to query your webhook URL.

If the curl request is successful, try running GitLab to send the WebHook request with the Test button. If there is nothing wrong, the message "Hook completed successfully: HTTP 200" will appear. If there is any error, a notification appears with error data.

After you call the hook using a push event, you can search the GitLab log (in production.log if your environment is production), for example WebHook Error => Failed to open TCP connection to 192.168.1.1:80 (No route to host - connect(2) for "192.168.1.1" port 80) .

If the curl request failed, try to find out what happened to your network. After fixing the error, GitLab WebHook requests should be sent successfully.

0
source share

More articles:


All Articles