Commit 6a59019e authored by Dat Tang's avatar Dat Tang 💡
Browse files

docs: Remove references to release.gitlab.net

parent 881db6d9

content/handbook/engineering/infrastructure-platforms/developer-experience/onboarding.md

+0 −2
Original line number Diff line number Diff line
@@ -41,7 +41,6 @@ and complete the issue. 
  * [Staging-canary](https://staging.gitlab.com) - `gitlab_canary=true`

  * [Staging-ref](https://staging-ref.gitlab.com)

  * [Preprod](https://pre.gitlab.com/)

  * [Release](https://release.gitlab.net)

  * [Customer-dot](https://customers.staging.gitlab.com/)

* CI environments

  * Main - Slack channel [#e2e-run-master](https://gitlab.slack.com/archives/CNV2N29DM)
@@ -61,7 +60,6 @@ These internal Slack channels may be helpful to join. 
  * [#infrastructure-managers](https://gitlab.slack.com/archives/C017BFF9CJU) - channel to communicate and collaborate with all engineering managers in Infrastructure

  * [#e2e-run-master](https://gitlab.slack.com/archives/CNV2N29DM) - channel with end-to-end test results on master pipeline

  * [#e2e-run-preprod](https://gitlab.slack.com/messages/CCNNKFP8B) - channel with  end-to-end test results for run against pre.gitlab.com

  * [#e2e-run-release](https://gitlab.slack.com/archives/C0154HCFLRE) - channel with end-to-end test results for run against release.gitlab.net

  * [#e2e-run-staging](https://gitlab.slack.com/messages/CBS3YKMGD) -  channel with  end-to-end test results for run against staging.gitlab.com

  * [#e2e-run-production](https://gitlab.slack.com/messages/CCNNKFP8B) - channel with end-to-end test results for run against gitlab.com

  * [#gpt-performance-run](https://gitlab.slack.com/messages/CH8J9EG49) - channel with performance testing results

content/handbook/engineering/infrastructure-platforms/environments/_index.md

+0 −11
Original line number Diff line number Diff line
@@ -130,17 +130,6 @@ copy of the production database. 
In addition, the `pre` environment is also used by SREs to validate infrastructure

changes, so it is important for the environment to match the configuration of `staging` and `production`.



### Release



| **Name** | **URL** | **Purpose** | **Deploy** | **Database** | **Terminal access** |

| ---- | --- | ------- | ------ | -------- | --------------- |

| release | release.gitlab.net | Deploying self-managed releases | Final monthly, patch and security releases | Separate and local | SREs |



The release environment is an environment used for validating security releases, self-managed final monthly and patch versions. It does not have a full production HA topology or a

copy of the production database.



The `release` environment receives and tests every package of the current milestone, i.e., every 16.1.X package until we tag 16.2.0.



### GitLab Team Services



| **Name** | **URL** | **Purpose** | **Deploy** | **Database** | **Terminal access** |

content/handbook/engineering/releases/monthly-releases/index.md

+3 −4
Original line number Diff line number Diff line
@@ -48,7 +48,7 @@ The end-to-end process consists on the following stages: 
1. **Release candidate** - A test [release candidate (RC)](#what-is-a-release-candidate-and-when-are-they-created) is created, along with a stable branch for the targeted [semver](https://semver.org) version. The release candidate package is built,

    tested and deployed to the [pre environment](/handbook/engineering/infrastructure-platforms/environments/#pre). A successful outcome indicates this package can be used as the final version. At this point [Release Managers](/handbook/engineering/releases/release-managers/) will

    announce the final commit to be included in the release.

1. **Tag** - Release Managers tag the final version of the release based on the release candidate. The release is built and deployed to the [Release environment](/handbook/engineering/infrastructure-platforms/environments/#release).

1. **Tag** - Release Managers tag the final version of the release based on the release candidate.

1. **Release** - On the release day, the release packages are published.



### Release Steps
@@ -122,15 +122,14 @@ Multiple tools are available to help determine if the merge request will be incl 
Merge requests included in a release candidate (RC) will be part of the monthly release. See ["What is a release candidate and when are they created?"](#what-is-a-release-candidate-and-when-are-they-created) for more information on release candidates. Merge requests will receive the `released::candidate` label to indicate their inclusion into the RC.



A merge request will receive the `released::published` label (which replaces the `released::candidate` label)

when included in the final release, such as `13.6.0` or `13.5.2`, and deployed to

[`release.gitlab.net`](/handbook/engineering/infrastructure-platforms/environments/#release).

when included in the final release, such as `13.6.0` or `13.5.2`.



### Merge request widget



The merge request widget shows the environment and the time of deployment in every merge request.

This provides information to understand where in the release process any merge request is:



* `release` is for the final version that is going out for self-managed users. When an MR is deployed to [`release.gitlab.net`](/handbook/engineering/infrastructure-platforms/environments/#release) instance, the `released::published` label is applied to the MR to indicate that it will be included in the upcoming monthly release.

* `release` is for the final version that is going out for self-managed users. When an MR is included in the final release, the `released::published` label is applied to the MR to indicate that it will be included in the upcoming monthly release.

* `pre` is for release candidates and versions that are used as a preparation for a final release for self-managed users. When an MR is included in a release candidate, the `released::candidate` label is applied to the MR to indicate that it will be included in the upcoming monthly release.



The merge request widget can also be used to reference where in the deployment process any merge request is:

content/handbook/engineering/testing/end-to-end-pipeline-monitoring.md

+0 −1
Original line number Diff line number Diff line
@@ -18,7 +18,6 @@ The test pipelines run on a scheduled basis, and their results are posted to Sla 
| CustomersDot Staging                     | [Pipelines](https://gitlab.com/gitlab-org/customers-gitlab-com/-/pipelines) \| [Definition](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/cce306c6e12f409a466dcebaad7037e62dd6d325/.gitlab/ci/e2e.gitlab-ci.yml#L236-276)                                                                                                                                                                  | Full       | [after each deployment to CustomersDot Staging](https://gitlab.com/gitlab-org/customers-gitlab-com/-/pipelines)                                                                                                                                                | [`#e2e-run-staging`](https://gitlab.slack.com/messages/CBS3YKMGD) [`#s_fulfillment_status`](https://gitlab.slack.com/messages/CL7SX4N86)    | [CustomersDot Staging](https://gitlab-qa-allure-reports.s3.amazonaws.com/cdot-e2e-staging/main/index.html)         |

| CustomersDot Production                  | [Pipelines](https://gitlab.com/gitlab-org/customers-gitlab-com/-/pipelines) \| [Definition](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/cce306c6e12f409a466dcebaad7037e62dd6d325/.gitlab/ci/e2e.gitlab-ci.yml#L298-324)                                                                                                                                                                  | Smoke      | [after each deployment to CustomersDot Production](https://gitlab.com/gitlab-org/customers-gitlab-com/-/pipelines)                                                                                                                                             | [`#e2e-run-production`](https://gitlab.slack.com/messages/CCNNKFP8B) [`#s_fulfillment_status`](https://gitlab.slack.com/messages/CL7SX4N86) | N/A                                                                                                                |

| Preprod                                  | [Pipelines](https://ops.gitlab.net/gitlab-org/quality/preprod/pipelines) \| [Definition](https://gitlab.com/gitlab-com/gl-infra/deployer/-/blob/2279042064c45fdb10ce696d1c4ef12b72affbfd/ci/environments/pre.yml#L171-181)                                                                                                                                                                             | Smoke      | [Every month for a few days before release, at 03:00 UTC](https://ops.gitlab.net/gitlab-org/quality/preprod/-/pipeline_schedules) and after [deployment to preprod](/handbook/engineering/infrastructure-platforms/environments/#pre) during Security and Patch releases | [`#e2e-run-preprod`](https://gitlab.slack.com/archives/CR7QH0RV1)                                                                           | [Preprod](https://gitlab-qa-allure-reports.s3.amazonaws.com/preprod-sanity/master/index.html)                      |

| Release                                  | [Pipelines](https://ops.gitlab.net/gitlab-org/quality/release) \| [Definition](https://gitlab.com/gitlab-com/gl-infra/deployer/-/blob/10cc4811f5aae0a38b77cd5c9def954a0e2afac1/ci/environments/release.yml#L82-93)                                                                                                                                                                                     | Smoke      | [Every month after the final release](https://ops.gitlab.net/gitlab-org/quality/release/-/pipeline_schedules) and after [deployment to Release](/handbook/engineering/infrastructure-platforms/environments/#release) during Security and Patch releases                 | [`#e2e-run-release`](https://gitlab.slack.com/archives/C0154HCFLRE)                                                                         | [Release](https://gitlab-qa-allure-reports.s3.amazonaws.com/release-sanity/master/index.html)                      |

| GitLab `master` `e2e:test-on-omnibus-ee` | [Pipelines](https://gitlab.com/gitlab-org/gitlab/pipelines) \| [Definition](https://gitlab.com/gitlab-org/gitlab/-/blob/77a5b0b3f8f910d4fe89a3fed46c4da53b1e587e/.gitlab/ci/qa.gitlab-ci.yml#L77-88)                                                                                                                                                                                                   | Full       | [scheduled pipeline every 2 hours](https://gitlab.com/gitlab-org/gitlab/pipeline_schedules)                                                                                                                                                                    | [`#e2e-run-master`](https://gitlab.slack.com/archives/CNV2N29DM)                                                                            | [Master EE](https://gitlab-qa-allure-reports.s3.amazonaws.com/e2e-test-on-omnibus/master/index.html)               |

| GitLab `master` `e2e:test-on-omnibus-ce` | [Pipelines](https://gitlab.com/gitlab-org/gitlab/-/pipeline_schedules) \| [Definition](https://gitlab.com/gitlab-org/gitlab/-/blob/77a5b0b3f8f910d4fe89a3fed46c4da53b1e587e/.gitlab/ci/qa.gitlab-ci.yml#L121-135)                                                                                                                                                                                      | Full       | [Daily at 4:00am UTC](https://gitlab.com/gitlab-org/gitlab/-/pipeline_schedules)                                                                                                                                                                               | [`#e2e-run-master`](https://gitlab.slack.com/archives/CNV2N29DM)                                                                            | [Master CE](https://gitlab-qa-allure-reports.s3.amazonaws.com/e2e-test-on-omnibus-ce/master/index.html)            |

| GitLab `master` `e2e:test-on-gdk`        | [Pipelines](https://gitlab.com/gitlab-org/gitlab/-/pipelines?ref=master&source=schedule) \| [Definition](https://gitlab.com/gitlab-org/gitlab/-/blob/77a5b0b3f8f910d4fe89a3fed46c4da53b1e587e/.gitlab/ci/qa.gitlab-ci.yml#L151-164)                                                                                                                                                                | Full       | [scheduled pipeline every 2 hours](https://gitlab.com/gitlab-org/gitlab/pipeline_schedules)                                                                                                                                                                    | [`#e2e-run-master`](https://gitlab.slack.com/archives/CNV2N29DM)                                                                            | [Master GDK](https://gitlab-qa-allure-reports.s3.amazonaws.com/e2e-test-on-gdk/master/index.html)                  |

content/handbook/engineering/testing/test-environments-catalog.md

+0 −21
Original line number Diff line number Diff line
@@ -224,27 +224,6 @@ Your GitLab account. 


---



### Release



| Type | Status | Platform | URL | Owner/DRI | Project | Access |

|------|--------|----------|-----|-----------|---------|--------|

| Permanent | Active | Self-Managed | [release.gitlab.net](https://release.gitlab.net) | Infrastructure Team | N/A | SREs |



**Purpose:** Self-managed release validation. Validates security releases, self-managed final monthly and patch versions.



**Key Features:**



- Single node omnibus installation

- Does not have full production HA topology or production database copy



**Automated Testing:**



- Runs smoke E2E test suite on deployment



[More details about Release](/handbook/engineering/infrastructure-platforms/environments/#release)



---



### Release Environments



| Type | Status | Platform | URL | Owner/DRI | Project | Access |