Release 12.1.11
Preparation
-
validate gitlab-org/omnibus-gitlab!3615 (merged) has been merged and is prepped in the 12-1-stable
branch -
Ensure builds are green on [Omnibus]
Packaging
-
Tag 12.1.11
:# In Slack: /chatops run release tag 12.1.11
-
While waiting for packages to build, now is a good time to prepare the blog post. Look at previous MRs for examples. => BLOG_POST_MR -
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
-
[Deploy] 12.1.11
to pre.gitlab.com. Note that starting in release 11.6 staging deploys are automatically triggered from the EE omnibus pipelinegitlab_com:upload_deploy
stage.# In Slack: /chatops run deploy 12.1.11-ee.0 --pre
-
Link to deployment job (even failed attempts) => https://ops.gitlab.net/gitlab-com/gl-infra/deployer/pipelines/81143
QA
The QA task issue is generated automatically when deploying to staging. If you need to manually generate the QA task, you can do so as follows:
# In Slack, replacing LAST_DEPLOYED_VERSION with the appropriate value:
/chatops run release qa vLAST_DEPLOYED_VERSION v12.1.11
Release
-
Publish the packages via ChatOps: # In Slack: /chatops run publish 12.1.11
-
Create the 12.1.11
version on version.gitlab.com -
Deploy the blog post -
In the #releases
channel, mention@contentteam
to tweet about the new release:"GitLab 12.1.11 is now available: [BLOG_POST_URL] [DESCRIPTION_OF_CHANGES]"
References
gitlab.com
- https://gitlab.com/gitlab-org/gitlab-foss/commits/12-1-stable
- https://gitlab.com/gitlab-org/gitlab/commits/12-1-stable-ee
- https://gitlab.com/gitlab-org/omnibus-gitlab/commits/12-1-stable
dev.gitlab.org
Edited by John Jarvis