Home → Problems →

Webhook from Github returns error (http status 500)

• Edit

dev-voko

02 Jun, 2014 09:28 AM

I've added a Github Webhook for rubydoc.info, but Github tells me that an error occured when calling the webhook:

Headers
Request URL: http://rubydoc.info/checkout
Request method: POST
content-type: application/json
Expect:
User-Agent: GitHub Hookshot 7654321
X-GitHub-Delivery: 12345678-1234-1234-1234-123456789012
X-GitHub-Event: ping
Payload
{ "zen": "Non-blocking is better than blocking.", "hook_id": 1234567 }

The response tells me "Oops! A Problem Occurred".

How do I setup a Github webhook to update the docs after a commit?

1. Support Staff 1 Posted by lsegal on 02 Jun, 2014 09:32 AM

   

   What is the full GitHub repository?

   • Edit

2. 2 Posted by dev-voko on 02 Jun, 2014 09:52 AM

   

   https://github.com/foodcoops/foodsoft

   Thanks for your fast response! If you need more info, please let me know.

   • Edit

3. Support Staff 3 Posted by lsegal on 02 Jun, 2014 09:58 AM

   

   Generating the repo seems to work for me: http://rubydoc.info/github/foodcoops/foodsoft/master/frames

   Are you still getting 500s? It might just have been a temporary issue.

   • Edit

4. 4 Posted by dev-voko on 02 Jun, 2014 10:05 AM

   

   The web interface works, but when setting up a Github webhook (to update
   the documentation after a new commit), the Github interface shows that
   there has been an error on the ping hook. Please see attached
   screenshots for more info.
   Or is it that this "ping" event is not supported?

   • jhbcdgjd.png 45.1 KB
   • cadhdbad.png 48.7 KB
   • Edit

5. Support Staff 5 Posted by lsegal on 02 Jun, 2014 10:08 AM

   

   It is supported, and does work. Please use the OFFICIAL RdocInfo Service through the Add Service button. Adding a custom service won't work if you don't provide the right parameters.

   • Edit

6. 6 Posted by dev-voko on 02 Jun, 2014 10:14 AM

   

   Thank you! I hoped that there would be a pre-built service, but it did
   not occur to me that Rdocinfo was the one. Thanks for your very quick help.

   • Edit

7. nap closed this discussion on 19 Aug, 2014 09:05 PM.