Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
fcb39b7d
Commit
fcb39b7d
authored
Mar 01, 2022
by
James Heimbuck
Committed by
Marcel Amirault
Mar 01, 2022
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add retry to troubleshooting for merge trains
parent
3fc460e4
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
0 deletions
+4
-0
doc/ci/pipelines/merge_trains.md
doc/ci/pipelines/merge_trains.md
+4
-0
No files found.
doc/ci/pipelines/merge_trains.md
View file @
fcb39b7d
...
...
@@ -201,6 +201,10 @@ the merged result is out of date and the pipeline can't be retried.
Instead, you should
[
add the merge request to the train
](
#add-a-merge-request-to-a-merge-train
)
again, which triggers a new pipeline.
If a job only fails intermittently, you can try using the
[
`retry`
](
../yaml/index.md#retry
)
keyword in the
`.gitlab-ci.yml`
file to have the job retried before the pipeline completes.
If it succeeds after a retry, the merge request is not removed from the merge train.
### Unable to add to merge train with message "The pipeline for this merge request failed."
Sometimes the
**Start/Add to merge train**
button is not available and the merge request says,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment