Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-12-03 09:09:47 +0300
committerGitLab Bot <gitlab-bot@gitlab.com>2020-12-03 09:09:47 +0300
commit9214e550c07793a8deb6d5cd5bb136d0d010a7ca (patch)
treebf094d583e9f57e2816a6f272bcbff302e264efe /doc
parente1e9056d03fec6d72771c7a4ba3fc1174b5ac009 (diff)
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc')
-rw-r--r--doc/user/project/integrations/webhooks.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/user/project/integrations/webhooks.md b/doc/user/project/integrations/webhooks.md
index 2aca15e04b9..4fc55d5afd9 100644
--- a/doc/user/project/integrations/webhooks.md
+++ b/doc/user/project/integrations/webhooks.md
@@ -68,7 +68,9 @@ If you are writing your own endpoint (web server) to receive
GitLab webhooks, keep in mind the following things:
- Your endpoint should send its HTTP response as fast as possible. If
- you wait too long, GitLab may decide the hook failed and retry it.
+ you wait too long (by default, a timeout of 10 seconds), GitLab may decide
+ the hook failed and retry it. You can configure this timeout with
+ `gitlab_rails['webhook_timeout']`.
- Your endpoint should ALWAYS return a valid HTTP response. If you do
not do this then GitLab thinks the hook failed and retries it.
Most HTTP libraries take care of this for you automatically but if