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
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-11-20 06:09:15 +0300
committerGitLab Bot <gitlab-bot@gitlab.com>2020-11-20 06:09:15 +0300
commitb0348fa2727fed578fc53d8d0c6d5f0177c799d5 (patch)
treebb7138043db1d1d275b8bdb7d55ac986df6cf129 /doc/ci/triggers
parent7a84f32e221939059ad4e34c7fecf3633f9ee448 (diff)
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/triggers')
-rw-r--r--doc/ci/triggers/README.md10
1 files changed, 9 insertions, 1 deletions
diff --git a/doc/ci/triggers/README.md b/doc/ci/triggers/README.md
index 9356e9f4614..10a1917d791 100644
--- a/doc/ci/triggers/README.md
+++ b/doc/ci/triggers/README.md
@@ -5,7 +5,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
type: tutorial
---
-# Triggering pipelines through the API
+# Triggering pipelines through the API **(CORE)**
Triggers can be used to force a pipeline rerun of a specific `ref` (branch or
tag) with an API call.
@@ -270,3 +270,11 @@ Old triggers, created before GitLab 9.0 are marked as legacy.
Triggers with the legacy label do not have an associated user and only have
access to the current project. They are considered deprecated and might be
removed with one of the future versions of GitLab.
+
+## Troubleshooting
+
+### '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 instead of a trigger token. [Add a new trigger](#adding-a-new-trigger)
+and use that token to authenticate when triggering a pipeline.