Skip to content

Updates and adds details on the packages for verification

John Skarbek requested to merge jts/update-package-counts into master
  • Updates the counts now that we are publishing more packages
  • Adds a summary section containing all the packages that ought to be there such that we can more easily identify what we are missing

It looks like this when the template is created:

CLICK ME!

Release 42.42.42

Preparation

  • Preparation MR's should already be created
  • Ensure any backports targeting 42.42.42 are merged to their stable counter part
  • Perform automated merging into the preparation branches: 
    # In Slack
/chatops run release merge 42.42.42
  • Merge the preparation merge requests
    • gitlab-org/gitlab
    • gitlab-org/omnibus-gitlab
  • Check the following list of critical issues/MRs which are to be included in 42.42.42.
    • REFERENCE_TO_MR_TO_PICK
  • Ensure builds are green on Omnibus

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

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 42.42.42-ee.0 --release

QA

If the patch release is deployed to release.gitlab.com, create a QA task issue by running the following chatops command:

# In Slack, replacing LAST_DEPLOYED_VERSION with the appropriate value:
/chatops run release qa v42.42.41 v42.42.42

This is not needed for backports that are not deployed to GitLab.com.

Release

  • Publish the packages via ChatOps: 
    # In Slack:
/chatops run publish 42.42.42
  • Verify that EE packages appear on packages.gitlab.com: EE (should contain 16 packages)
  • Verify that CE packages appear on packages.gitlab.com: CE (should contain 14 packages)
Package Names (expanded)
Edition Package Name Distro
CE gitlab-ce-42.42.42-ce.0.el6.x86_64.rpm el/6
CE gitlab-ce-42.42.42-ce.0.el6.x86_64.rpm ol/6
CE gitlab-ce-42.42.42-ce.0.el6.x86_64.rpm scientific/6
CE gitlab-ce-42.42.42-ce.0.el7.x86_64.rpm el/7
CE gitlab-ce-42.42.42-ce.0.el7.x86_64.rpm ol/7
CE gitlab-ce-42.42.42-ce.0.el7.x86_64.rpm scientific/7
CE gitlab-ce-42.42.42-ce.0.el8.x86_64.rpm el/8
CE gitlab-ce-42.42.42-ce.0.sles15.x86_64.rpm opensuse/15.1
CE gitlab-ce_42.42.42-ce.0_amd64.deb debian/buster
CE gitlab-ce_42.42.42-ce.0_amd64.deb debian/jessie
CE gitlab-ce_42.42.42-ce.0_amd64.deb debian/stretch
CE gitlab-ce_42.42.42-ce.0_amd64.deb ubuntu/bionic
CE gitlab-ce_42.42.42-ce.0_amd64.deb ubuntu/focal
CE gitlab-ce_42.42.42-ce.0_amd64.deb ubuntu/xenial
EE gitlab-ee-42.42.42-ee.0.el6.x86_64.rpm el/6
EE gitlab-ee-42.42.42-ee.0.el6.x86_64.rpm ol/6
EE gitlab-ee-42.42.42-ee.0.el6.x86_64.rpm scientific/6
EE gitlab-ee-42.42.42-ee.0.el7.x86_64.rpm el/7
EE gitlab-ee-42.42.42-ee.0.el7.x86_64.rpm ol/7
EE gitlab-ee-42.42.42-ee.0.el7.x86_64.rpm scientific/7
EE gitlab-ee-42.42.42-ee.0.el8.x86_64.rpm el/8
EE gitlab-ee-42.42.42-ee.0.sles12.x86_64.rpm sles/12.2
EE gitlab-ee-42.42.42-ee.0.sles12.x86_64.rpm sles/12.5
EE gitlab-ee-42.42.42-ee.0.sles15.x86_64.rpm opensuse/15.1
EE gitlab-ee_42.42.42-ee.0_amd64.deb debian/buster
EE gitlab-ee_42.42.42-ee.0_amd64.deb debian/jessie
EE gitlab-ee_42.42.42-ee.0_amd64.deb debian/stretch
EE gitlab-ee_42.42.42-ee.0_amd64.deb ubuntu/bionic
EE gitlab-ee_42.42.42-ee.0_amd64.deb ubuntu/focal
EE gitlab-ee_42.42.42-ee.0_amd64.deb ubuntu/xenial
  • Verify that Docker images appear on hub.docker.com: EE / CE
  • Create the 42.42.42 version on version.gitlab.com
  • Deploy the blog post
  • In the #content-updates channel, share a link to the blog post URL.

References

gitlab.com

dev.gitlab.org

Merge request reports