Release 12.2.2

Preparation

• Preparation MR's should already be created
• Ensure any backports targeting 12.2.2 are merged to their stable counter part
  • CE Backports
  • EE Backports
  • Omnibus CE
  • Omnibus EE
• Perform automated merging into the preparation branches:

  # In Slack
  /chatops run release merge 12.2.2

• Merge the preparation branches
• For omnibus-gitlab add the changes to the stable branches: cherry-pick remaining merge requests directly into the stable branch.
• Check the following list of critical issues/MRs which are to be included in 12.2.2.
  • gitlab-org/omnibus-gitlab!3551 (merged)
• Ensure builds are green on Omnibus

Packaging

• Check if mirroring synced stable branches to dev

  • CE
  • EE
  • Omnibus

• Tag 12.2.2:

  # In Slack:
  /chatops run release tag 12.2.2

• 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.2.2 to pre.gitlab.com. Note that starting in release 11.6 staging deploys are automatically triggered from the EE omnibus pipeline gitlab_com:upload_deploy stage.

  # In Slack:
  /chatops run deploy 12.2.2-ee.0 --pre

• Link to deployment job (even failed attempts) =>

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.2.2

Release

• Publish the packages via ChatOps:

  # In Slack:
  /chatops run publish 12.2.2

• Verify that packages appear on packages.gitlab.com: EE / CE

• Verify that Docker images appear on hub.docker.com: EE / CE

• Create the 12.2.2 version on version.gitlab.com

• Deploy the blog post

• In the #releases channel, mention @contentteam to tweet about the new release:

  "GitLab 12.2.2 is now available: [BLOG_POST_URL] [DESCRIPTION_OF_CHANGES]"

References

gitlab.com

• https://gitlab.com/gitlab-org/gitlab-ce/commits/12-2-stable
• https://gitlab.com/gitlab-org/gitlab-ee/commits/12-2-stable-ee
• https://gitlab.com/gitlab-org/omnibus-gitlab/commits/12-2-stable

dev.gitlab.org

• https://dev.gitlab.org/gitlab/gitlabhq/commits/12-2-stable
• https://dev.gitlab.org/gitlab/gitlab-ee/commits/12-2-stable-ee
• https://dev.gitlab.org/gitlab/omnibus-gitlab/commits/12-2-stable