Subject: Are service hooks down?
Original Post
Josh
I have service hooks setup for various projects and they dont seem to be triggering at all. I tried the test hook command in Github as well and dont see a single request in any of my logs.
Is this feature down and, if so, is there a way to receive notifications if it is down in the future?
Regards,
jl
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Tekkub on 24 Jul, 2009 12:43 AM
They've been working for me. What repo(s) are giving you trouble, and are you pushing new branches or existing ones?
3 Posted by Josh on 24 Jul, 2009 06:59 PM
I'm trying it with almost all my repos, but in particular, wripple and wripple-beta.
It's VERY odd. When I setup a tunnlr account to test out the code on my local machine and do a test payload after added the tunnlr URL service hook, I wait a few seconds, watch my mongrel log, and I see the payload.
HOWEVER, when I try using the production server with the following type of service hook URL: http://www.wripple.com/sp/github/2557a2fe-787f-11de-995e-40403dec6bdc
and test the payload or do a commit, NOTHING. It makes no sense.
I have checked the production.log and my nginx access logs after trying the payload 5 times and I am not showing a SINGLE post or request for that matter from Github.
How are you doing the POST? Could your server somehow be blocked?
Support Staff 4 Posted by Tekkub on 26 Jul, 2009 02:42 AM
Just curious, if you try a simpler path does it work? I don't think our side should be picky about the URL's contents, but something might be amiss.
We don't block anything on our side, and I do know that hooks are running for my own repos.
5 Posted by Josh on 26 Jul, 2009 01:48 PM
Shorter URL doesnt seem to matter, however, (and this is truly weird), if a different Wripple client uses the same type of service hook URL that we are generating, it WORKS for them!!!
Could it be private versus public projects? Could I have a bad setting turned on for my project?
Thanks!
/j
6 Posted by Josh on 27 Jul, 2009 07:28 PM
I just thought of something. Not sure if it has any bearing on what is going on.
I have TWO repos setup on Github for my Wripple project - production and beta. I use the same SOURCE project for both and then either push to beta or push to production for deployment and testing.
Could this be the cause of the problem? Could the fact that the same project commiting to the same git repo locally but pusing to two different github repos cause service hooks to fail?
Thanks,
Josh
Support Staff 7 Posted by defunkt on 30 Jul, 2009 09:00 PM
Hi Josh,
That might be an issue. The typical way to do this in Git is to use branches. Many people have production, beta, staging, and other versions of the same project all hosted within the same repository.
I noticed the webhook URL has no dashes in it anymore - did changing it fix your issue?
Cheers,
Chris
8 Posted by Josh on 01 Aug, 2009 12:21 PM
Chris-
Yeah I am just learning about that. Have started branching like a mad man and deleted the second repo. It seems like the hooks are beginning to work now.
Thanks!
Josh