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
38891633
Commit
38891633
authored
May 16, 2019
by
Rémy Coutable
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document what to do if review jobs keep failing
Signed-off-by:
Rémy Coutable
<
remy@rymai.me
>
parent
0795742f
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
6 deletions
+16
-6
doc/development/testing_guide/review_apps.md
doc/development/testing_guide/review_apps.md
+16
-6
No files found.
doc/development/testing_guide/review_apps.md
View file @
38891633
...
@@ -78,17 +78,27 @@ subgraph CNG-mirror pipeline
...
@@ -78,17 +78,27 @@ subgraph CNG-mirror pipeline
**Additional notes:**
**Additional notes:**
-
The Kubernetes cluster is connected to the
`gitlab-{ce,ee}`
projects using
-
If the
`review-deploy`
job keep failing (note that we already retry it twice),
[
GitLab's Kubernetes integration
][
gitlab-k8s-integration
]
. This basically
please post a message in the
`#quality`
channel and/or create a ~Quality ~bug
allows to have a link to the Review App directly from the merge request
issue with a link to your merge request. Note that the deployment failure can
widget.
reveal an actual problem introduced in your merge request (i.e. this isn't
-
If the Review App deployment fails, you can simply retry it (there's no need
necessarily a transient failure)!
to run the
[
`review-stop`
][
gitlab-ci-yml
]
job first).
-
If the
`review-qa-smoke`
job keep failing (note that we already retry it twice),
please check the job's logs: you could discover an actual problem introduced in
your merge request. You can also download the artifacts to see screenshots of
the page at the time the failures occurred. If you don't find the cause of the
failure or if it seems unrelated to your change, please post a message in the
`#quality`
channel and/or create a ~Quality ~bug issue with a link to your
merge request.
-
The manual
[
`review-stop`
][
gitlab-ci-yml
]
in the
`test`
stage can be used to
-
The manual
[
`review-stop`
][
gitlab-ci-yml
]
in the
`test`
stage can be used to
stop a Review App manually, and is also started by GitLab once a merge
stop a Review App manually, and is also started by GitLab once a merge
request's branch is deleted after being merged.
request's branch is deleted after being merged.
-
Review Apps are cleaned up regularly via a pipeline schedule that runs
-
Review Apps are cleaned up regularly via a pipeline schedule that runs
the
[
`schedule:review-cleanup`
][
gitlab-ci-yml
]
job.
the
[
`schedule:review-cleanup`
][
gitlab-ci-yml
]
job.
-
The Kubernetes cluster is connected to the
`gitlab-{ce,ee}`
projects using
[
GitLab's Kubernetes integration
][
gitlab-k8s-integration
]
. This basically
allows to have a link to the Review App directly from the merge request
widget.
## QA runs
## QA runs
...
...
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