diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-03-31 18:08:50 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-03-31 18:08:50 +0300 |
commit | ccab6fb4df8bc12220334618e56d911c4d0e447c (patch) | |
tree | a8c7bb66fb4c36c97e7e1b4f27744fcd93c3bcf3 /doc/ci | |
parent | 820c5f6d5c816ba4b742f2ae2e08cc548314531a (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci')
-rw-r--r-- | doc/ci/triggers/index.md | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/ci/triggers/index.md b/doc/ci/triggers/index.md index 393b128c658..b9e5dd87b24 100644 --- a/doc/ci/triggers/index.md +++ b/doc/ci/triggers/index.md @@ -187,7 +187,12 @@ In pipelines triggered with a trigger token, jobs are labeled as `triggered` in ## Troubleshooting -### `404 not found` when triggering a pipeline +### `403 Forbidden` when you trigger a pipeline with a webhook + +When you trigger a pipeline with a webhook, the API might return a `{"message":"403 Forbidden"}` response. +To avoid trigger loops, do not use [pipeline events](../../user/project/integrations/webhook_events.md#pipeline-events) to trigger pipelines. + +### `404 Not Found` when triggering a pipeline A response of `{"message":"404 Not Found"}` when triggering a pipeline might be caused by using a [personal access token](../../user/profile/personal_access_tokens.md) |