debian-mirror-gitlab/doc/development/documentation/review_apps.md

stage	group	info	description
none	Documentation Guidelines	To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments	Learn how documentation review apps work.

Documentation review apps

If you're a GitLab team member and your merge request contains documentation changes, you can use a review app to preview how they would look if they were deployed to the GitLab Docs site.

Review apps are enabled for the following projects:

• GitLab
• Omnibus GitLab
• GitLab Runner
• GitLab Charts

Alternatively, check the gitlab-docs development guide or the GDK documentation to render and preview the documentation locally.

How to trigger a review app

If a merge request has documentation changes, use the review-docs-deploy manual job to deploy the documentation review app for your merge request.

The review-docs-deploy* job triggers a cross project pipeline and builds the docs site with your changes. When the pipeline finishes, the review app URL appears in the merge request widget. Use it to navigate to your changes.

The review-docs-cleanup job is triggered automatically on merge. This job deletes the review app.

You must have the Developer role in the project. Users without the Developer role, such as external contributors, cannot run the manual job. In that case, ask someone from the GitLab team to run the job.

Technical aspects

If you want to know the in-depth details, here's what's really happening:

1. You manually run the review-docs-deploy job in a merge request.
2. The job runs the scripts/trigger-build.rb script with the docs deploy flag, which triggers the "Triggered from gitlab-org/gitlab 'review-docs-deploy' job" pipeline trigger in the gitlab-org/gitlab-docs project for the $DOCS_BRANCH (defaults to main).
3. The preview URL is shown both at the job output and in the merge request widget. You also get the link to the remote pipeline.
4. In the gitlab-org/gitlab-docs project, the pipeline is created and it skips most test jobs to lower the build time.
5. After the docs site is built, the HTML files are uploaded as artifacts to a GCP bucket (see issue gitlab-com/gl-infra/reliability#11021 for the implementation details).

The following GitLab features are used among others:

• Manual jobs
• Multi project pipelines
• Review Apps
• Artifacts
• Merge request pipelines

Troubleshooting review apps

NoSuchKey The specified key does not exist

If you see the following message in a review app, either the site is not yet deployed, or something went wrong with the downstream pipeline in gitlab-docs.

NoSuchKeyThe specified key does not exist.No such object: <URL>

In that case, you can:

• Wait a few minutes and the review app should appear online.
• Check the review-docs-deploy job's log and verify the URL. If the URL shown in the merge request UI is different than the job log, try the one from the job log.
• Check the status of the remote pipeline from the link in the merge request's job output. If the pipeline failed or got stuck, GitLab team members can ask for help in the #docs internal Slack channel. Contributors can ping a technical writer in the merge request.