Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
GitLab
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
GitLab.org
GitLab
Commits
9141a0e1
Commit
9141a0e1
authored
4 years ago
by
Brie Carranza
Committed by
Marcel Amirault
4 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Docs: Add and populate troubleshooting section for triggering pipelines
parent
20ee0b94
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/ci/triggers/README.md
+9
-1
9 additions, 1 deletion
doc/ci/triggers/README.md
with
9 additions
and
1 deletion
doc/ci/triggers/README.md
+
9
−
1
View file @
9141a0e1
...
...
@@ -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.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment