From 02edb0b990cf3c8ef65381426e9cc003913b1c8c Mon Sep 17 00:00:00 2001
From: ddavison <ddavison@gitlab.com>
Date: Fri, 7 Feb 2025 11:46:08 -0500
Subject: [PATCH] Rename Quality to DevEx

---
 .gitlab/merge_request_templates/Release.md | 2 +-
 README.md                                  | 2 +-
 docs/release_process.md                    | 4 ++--
 docs/what_tests_can_be_run.md              | 4 ++--
 lib/gitlab/qa/component/base.rb            | 2 +-
 5 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/.gitlab/merge_request_templates/Release.md b/.gitlab/merge_request_templates/Release.md
index e2bf407d..79d83602 100644
--- a/.gitlab/merge_request_templates/Release.md
+++ b/.gitlab/merge_request_templates/Release.md
@@ -12,7 +12,7 @@ https://gitlab.com/gitlab-org/gitlab-qa/-/compare/<PREVIOUS_VERSION>...<COMMIT_U
 
 ## Post-merge checklist
 
-- [ ] In the `pipeline-common` project, [update the GITLAB_QA_VERSION](https://gitlab.com/gitlab-org/quality/pipeline-common/-/blob/master/ci/base.gitlab-ci.yml) (make sure to add a `Changelog:` trailer to the commit) and [create a release](https://gitlab.com/gitlab-org/quality/pipeline-common#release-process).
+- [ ] In the `pipeline-common` project, [update the GITLAB_QA_VERSION](https://gitlab.com/gitlab-org/dx/pipeline-common/-/blob/master/ci/base.gitlab-ci.yml) (make sure to add a `Changelog:` trailer to the commit) and [create a release](https://gitlab.com/gitlab-org/dx/pipeline-common#release-process).
 - [ ] Unless already done by [`renovate-gitlab-bot`](https://gitlab.com/dashboard/merge_requests?scope=all&state=opened&author_username=gitlab-dependency-update-bot&label_name[]=Engineering%20Productivity), in the GitLab project, update the ref for `pipeline-common` in [`.gitlab/ci/qa-common/main.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/ci/qa-common/main.gitlab-ci.yml).
 - [ ] Unless already done by [`renovate-gitlab-bot`](https://gitlab.com/dashboard/merge_requests?scope=all&state=opened&author_username=gitlab-dependency-update-bot&label_name[]=Quality), or if you need it sooner, in the GitLab project, update the `gitlab-qa` gem version in [`qa/Gemfile`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/qa/Gemfile) and [`qa/Gemfile.lock`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/qa/Gemfile.lock) (for an example, see: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/117054).
 
diff --git a/README.md b/README.md
index 586c7e18..96378a13 100644
--- a/README.md
+++ b/README.md
@@ -100,7 +100,7 @@ Currently, we execute the test suite against GitLab Docker images created by
 Omnibus nightly via a [`gitlab-org/gitlab` nightly schedule pipeline](https://gitlab.com/gitlab-org/gitlab/-/pipeline_schedules).
 
 We also execute the test suite nightly against our [staging environment](https://staging.gitlab.com)
-via a pipeline in the [staging project](https://gitlab.com/gitlab-org/quality/staging).
+via a pipeline in the [staging project](https://gitlab.com/gitlab-org/test-monitoring/staging).
 
 Finally, we trigger GitLab QA pipelines whenever someone clicks `package-and-qa` manual
 action in a merge request.
diff --git a/docs/release_process.md b/docs/release_process.md
index c9fa5807..cbd654cf 100644
--- a/docs/release_process.md
+++ b/docs/release_process.md
@@ -36,7 +36,7 @@ Note: The `gem-release` job uses:
 
 ## Post-release maintenance
 
-Please note that `gitlab-qa` version in `gitlab-org/gitlab` project will be updated automatically by [renovate-gitlab-bot](https://gitlab.com/gitlab-org/frontend/renovate-gitlab-bot). However, for live environment pipelines we need to specify the version in [pipeline-common](https://gitlab.com/gitlab-org/quality/pipeline-common) project manually. Remember to open an MR updating `GITLAB_QA_VERSION` value in [base.gitlab-ci.yml](https://gitlab.com/gitlab-org/quality/pipeline-common/-/blob/master/ci/base.gitlab-ci.yml#L4) shortly after the new version is released.
+Please note that `gitlab-qa` version in `gitlab-org/gitlab` project will be updated automatically by [renovate-gitlab-bot](https://gitlab.com/gitlab-org/frontend/renovate-gitlab-bot). However, for live environment pipelines we need to specify the version in [pipeline-common](https://gitlab.com/gitlab-org/dx/pipeline-common) project manually. Remember to open an MR updating `GITLAB_QA_VERSION` value in [base.gitlab-ci.yml](https://gitlab.com/gitlab-org/dx/pipeline-common/-/blob/master/ci/base.gitlab-ci.yml#L4) shortly after the new version is released.
 
 ## Flowchart
 
@@ -74,7 +74,7 @@ flowchart LR
     classDef linkNode color:blue,text-decoration:underline;
     class P linkNode;
 
-    click P "https://gitlab.com/gitlab-org/quality/pipeline-common/-/tree/master#release-process"
+    click P "https://gitlab.com/gitlab-org/dx/pipeline-common/-/tree/master#release-process"
 ```
 
 [`lib/gitlab/qa/version.rb`]: https://gitlab.com/gitlab-org/gitlab-qa/blob/master/lib/gitlab/qa/version.rb#L3
diff --git a/docs/what_tests_can_be_run.md b/docs/what_tests_can_be_run.md
index aa60b477..3c75be54 100644
--- a/docs/what_tests_can_be_run.md
+++ b/docs/what_tests_can_be_run.md
@@ -43,9 +43,9 @@ All environment variables used by GitLab QA should be defined in [`lib/gitlab/qa
 | `GITLAB_ADMIN_USERNAME` |-  | Admin username to use when adding a license. | No|
 | `GITLAB_ADMIN_PASSWORD` |-  | Admin password to use when adding a license. | No|
 | `GITLAB_SANDBOX_NAME`   | `gitlab-qa-sandbox` | The sandbox group name the test suite is going to use. | No|
-| `GITLAB_QA_ACCESS_TOKEN`|-  | A valid personal access token with the `api` scope. This allows tests to use the API without having to create a new personal access token first. It is also used to check what version [deployed environments](https://gitlab.com/gitlab-org/quality/pipeline-common/-/blob/master/ci/dot-com/README.md#projects) are currently running. Existing tokens for each environment can be found in the shared 1Password vault. |No|
+| `GITLAB_QA_ACCESS_TOKEN`|-  | A valid personal access token with the `api` scope. This allows tests to use the API without having to create a new personal access token first. It is also used to check what version [deployed environments](https://gitlab.com/gitlab-org/dx/pipeline-common/-/blob/master/ci/dot-com/README.md#projects) are currently running. Existing tokens for each environment can be found in the shared 1Password vault. |No|
 | `GITLAB_QA_ADMIN_ACCESS_TOKEN` |-  | A valid personal access token with the `api` scope from a user with admin access. Used for API access as an admin during tests. | No|
-| `GITLAB_QA_CONTAINER_REGISTRY_ACCESS_TOKEN` | - | A valid personal access token with the `read_registry` scope. Used to [access the container registry on `registry.gitlab.com` when tests run in a CI job that _is not_ triggered via another pipeline](https://gitlab.com/gitlab-org/gitlab-qa/-/blob/364addb83e7b136ff0f9d8719ca9553d290aa9ab/lib/gitlab/qa/release.rb#L152). For example, if you manually run a [new Staging pipeline](https://ops.gitlab.net/gitlab-org/quality/staging/-/pipelines/new), this token will be used. | No |
+| `GITLAB_QA_CONTAINER_REGISTRY_ACCESS_TOKEN` | - | A valid personal access token with the `read_registry` scope. Used to [access the container registry on `registry.gitlab.com` when tests run in a CI job that _is not_ triggered via another pipeline](https://gitlab.com/gitlab-org/gitlab-qa/-/blob/364addb83e7b136ff0f9d8719ca9553d290aa9ab/lib/gitlab/qa/release.rb#L152). For example, if you manually run a [new Staging pipeline](https://ops.gitlab.net/gitlab-org/test-monitoring/staging/-/pipelines/new), this token will be used. | No |
 | `EE_LICENSE` |-  | Enterprise Edition license. For Staging license to be applied successfully requires `CUSTOMER_PORTAL_URL` set. | No|
 | `GITLAB_LICENSE_MODE` |- | If set to `test` gitlab-qa will then set customers portal address to Staging address. | No|
 | `QA_EE_ACTIVATION_CODE` |-  | Cloud activation code to enable Enterprise Edition features. | No|
diff --git a/lib/gitlab/qa/component/base.rb b/lib/gitlab/qa/component/base.rb
index d7afd33c..2029d64e 100644
--- a/lib/gitlab/qa/component/base.rb
+++ b/lib/gitlab/qa/component/base.rb
@@ -206,7 +206,7 @@ module Gitlab
               unless reconfigure_log_file.nil?
                 Runtime::Logger.info(
                   "Follow the document " \
-                  "https://gitlab.com/gitlab-org/quality/runbooks/-/blob/main/debug_orchestrated_test_locally/ " \
+                  "https://gitlab.com/gitlab-org/dx/runbooks/-/blob/main/debug_orchestrated_test_locally/ " \
                   "for debugging the test failure locally.")
 
                 # Tailing the reconfigure logs after retries are over and before raising exception
-- 
GitLab