Thats a very good idea, I didn't think of it, I can set it up and try it.
Thank you for that.
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to gitlabhq+unsubscr...@goo
You could test the theory, though, by setting up a dummy receiver and
seeing if that also reverberates.
On Oct 27, 2015 8:11 AM, "Gordon Murray" wrote:
> Thanks for replying, good to know its not just me!
>
> In this case, I can't control the response time for GitLab's webhook, we
> have DeployHQ
Thanks for replying, good to know its not just me!
In this case, I can't control the response time for GitLab's webhook, we
have DeployHQ set up to receive it. I will contact DeployHQ and see if they
can help in any way.
Gordon.
--
You received this message because you are subscribed to the G
Yes, I and others have seen webhooks reverberate. The key to avoiding what
I ran into seems to be to make sure the receiver replies immediately.
Does it still happen if you point to a null webhooks that just immediately
returns success?
Also, supposedly there is a timeout you can increase.
- Dan
Hi,
I have recently begun using Gitlab and I have a webhook set up to call
DeployHQ upon commit to the repository.
However, over the weekend I noticed it was repeatedly calling the webhook
even though there was no activity in the repository.
I have the webhook set up for 'Push Events' only, no
