From bc6cffdd9057483b7002de1c475f014ac5d7e6cd Mon Sep 17 00:00:00 2001 From: Mohamed Hamda <mhamda@gitlab.com> Date: Thu, 11 May 2023 08:47:36 +0200 Subject: [PATCH] Update database_migration_pipeline.md docs Add a note about having the "database" label --- doc/development/database/database_migration_pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/development/database/database_migration_pipeline.md b/doc/development/database/database_migration_pipeline.md index 2344ee3f942c7..70f9c1523c09d 100644 --- a/doc/development/database/database_migration_pipeline.md +++ b/doc/development/database/database_migration_pipeline.md @@ -15,7 +15,7 @@ It is based on an [architecture blueprint](../../architecture/blueprints/databas Migration testing is enabled in the [GitLab project](https://gitlab.com/gitlab-org/gitlab) for changes that add a new database migration. Trigger this job manually by running the `db:gitlabcom-database-testing` job within in `test` stage. To avoid wasting resources, -only run this job when your MR is ready for review. +only run this job when your MR is ready for review. Additionally, ensure that the MR has the "database" label for the pipeline to appear in the test stage. The job starts a pipeline on the [ops GitLab instance](https://ops.gitlab.net/). For security reasons, access to the pipeline is restricted to database maintainers. -- GitLab