Release 12.9.7
Preparation
- Preparation MR's should already be created
- Merge the following MR's to address this issue:
Version | MR 1: Add project group and ancestors to group list | MR 2: Remove check for user being applicable codeowner | MR 3: Add feature flag for CODEOWNERS validations for web requests |
---|---|---|---|
master | gitlab-org/gitlab!31152 (merged) | gitlab-org/gitlab!31768 (merged) | gitlab-org/gitlab!31283 (merged) (restores check) |
12.10 | gitlab-org/gitlab!31804 (closed) | gitlab-org/gitlab!31809 (merged) | gitlab-org/gitlab!31822 (merged) |
12.9 | gitlab-org/gitlab!31806 (merged) | gitlab-org/gitlab!31808 (merged) | gitlab-org/gitlab!31823 (merged) |
-
create one-off branches from each 12-10-stable and 12-9-stable branches with the appropriate GitLab sha
in theVERSION
file- Do not utilize the existing stable branches in
omnibus-gitlab
as this would otherwise pollute that branch - This will enable omnibus to build docker images we need for validation
- https://dev.gitlab.org/gitlab/omnibus-gitlab/-/commit/57986e764c1a2fb31eec7e7dbbe6f427d9bacc15
- Do not utilize the existing stable branches in
-
Allow a build to occur: https://dev.gitlab.org/gitlab/omnibus-gitlab/pipelines/154367 -
Notify groupsource code and Security in #1348 (closed) to begin testing -
Address issues if new items are found
-
Proceed below to perform the release
Packaging
-
Check if mirroring synced stable branches to dev. If the output is ✅ for every repo, we can proceed to tag.# In Slack /chatops run mirror status
-
Tag 12.9.7
:# In Slack: /chatops run release tag 12.9.7
-
While waiting for packages to build, now is a good time to prepare the blog post. Look at previous MRs for examples. => gitlab-com/www-gitlab-com!49707 (merged) -
Check progress of EE packages build and CE packages build. - This might take a while (around 80 min).
- We only need the EE packages to finish to continue with next steps.
Deploy
For patch releases, the only available environment for deploys is pre.gitlab.com
. All GitLab Inc. team members can login to that installation using their email address (through google oauth).
pre.gitlab.com
Deployments to pre.gitlab.com are performed automatically.
Instructions to manually deploy if required.
If you need to manually run a deployment, you can do so as follows:
# In Slack:
/chatops run deploy 12.9.7-ee.0 --pre
QA
The QA issue is created automatically, and linked as a related issue.
Instructions to manually generate QA issue if required.
If the QA task issue needs to be manually generated, you can do so as follows:
# In Slack, replacing LAST_DEPLOYED_VERSION with the appropriate value:
/chatops run release qa vLAST_DEPLOYED_VERSION v12.9.7
Release
-
Publish the packages via ChatOps: # In Slack: /chatops run publish 12.9.7
-
Verify that packages appear on packages.gitlab.com
: EE / CE -
Verify that Docker images appear on hub.docker.com
: EE / CE -
Create the 12.9.7
version on version.gitlab.com - [-] Deploy the blog post
- [-] In the
#content-updates
channel, share a link to the blog post::tada: GitLab 12.9.7 has been released: BLOG_POST_URL
References
gitlab.com
- https://gitlab.com/gitlab-org/gitlab-foss/commits/12-9-stable
- https://gitlab.com/gitlab-org/gitlab/commits/12-9-stable-ee
- https://gitlab.com/gitlab-org/omnibus-gitlab/commits/12-9-stable