Release 15.5.1

Preparation

• Preparation MR's should already be created
• Ensure 15-5-stable-ee GitLab branch is green.
• Ensure any backports targeting 15.5.1 are merged to their stable counter part
  • GitLab Backports
  • Omnibus
  • CNG
  • Gitaly
• Perform automated merging into the preparation branches:

  # In Slack
  /chatops run release merge 15.5.1

• Check for any MR's that might have been created that are targeting our preparation branch
  • GitLab
  • Omnibus
  • CNG
  • Gitaly
• Merge the preparation merge requests
  • gitlab-org/gitlab
  • gitlab-org/omnibus-gitlab
  • gitlab-org/build/CNG
• Check the following list of critical issues/MRs which are to be included in 15.5.1.
  • gitlab-org/gitlab!101824 (merged)
• Ensure that any post-deploy migrations in the stable branch have been executed on GitLab.com by executing the post-deploy migration pipeline: /chatops run post_deploy_migrations execute.
• Ensure builds are green on Omnibus

Backport request

If this patch release is part of a backport request, we will not be able to deploy the package to our release instance. Now is the time to kick off QA. Refer to the backport QA testing documentation to complete this task:

• QA is complete, and sign-off by the current QA on-call is noted as a comment on this issue.

Packaging

• Check if mirroring synced stable branches to dev. If the output is ✅ for every repo, we can proceed to tag. Note. If GitLab Canonical to Security mirroring has diverged due to security merges this mirror is expected to show as a broken and can be safely ignored.

  # In Slack
  /chatops run mirror status

• Tag 15.5.1:

  # In Slack:
  /chatops run release tag 15.5.1

• 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!113683 (merged)

• Check progress of EE packages build and CE packages build.

  • /chatops run release status 15.5.1
  • 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 release.gitlab.net. All GitLab Inc. team members can login to that installation using their email address (through google oauth).

Deployment to release.gitlab.net is not required if the patch release is not for the latest completed monthly release version. This is because release.gitlab.net will be on the latest monthly release, and deploying a patch of an older version will require rolling back release.gitlab.net.

release.gitlab.net

Deployments to release.gitlab.net 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 15.5.1-ee.0 release

Release

• Publish the packages via ChatOps:

  # In Slack:
  /chatops run publish 15.5.1

• Verify the check-packages job completes successfully on the EE Pipeline
• Verify the check-packages job completes successfully on the CE Pipeline
• Verify that Docker images appear on hub.docker.com: EE / CE
• Deploy the blog post
• Create the 15.5.1 version on version.gitlab.com

References

gitlab.com

• https://gitlab.com/gitlab-org/gitlab-foss/commits/15-5-stable
• https://gitlab.com/gitlab-org/gitlab/commits/15-5-stable-ee
• https://gitlab.com/gitlab-org/omnibus-gitlab/commits/15-5-stable

dev.gitlab.org

• https://dev.gitlab.org/gitlab/gitlabhq/commits/15-5-stable
• https://dev.gitlab.org/gitlab/gitlab-ee/commits/15-5-stable-ee
• https://dev.gitlab.org/gitlab/omnibus-gitlab/commits/15-5-stable

Release Certification

The release certification process may apply to this release. cc @gitlab-com/gl-security/federal-application-security