Skip to content

Third test rollout of Ruby 3.1 package to gstg-ref, gstg-cny

Proposal

Deploy a Ruby 3.1 package to gstg-ref before the planned production rollout.

During the 2nd test rollout gstg-ref was broken and we couldn't verify Sidekiq running on Ruby 3.1. This test rollout will help gives us confidence of running Sidekiq with Ruby 3.1.

Deploy to gstg-ref (and gstg-cny)

  • Run git commit --allow-empty -m "Empty commit to trigger a new auto-deploy pkg" to add an extra commit to the Omnibus or CNG auto deploy branch.
  • Trigger a deployment pipeline by running the "MANUAL auto-deploy pick&tag" inactive manual scheduled pipeline: https://ops.gitlab.net/gitlab-org/release/tools/-/pipeline_schedules/.
  • Cancel the packager pipelines created in the previous step and manually start new pipelines on the same tags. Set the following variables when starting the pipeline: USE_NEXT_RUBY_VERSION_IN_AUTODEPLOY to true and NEXT_RUBY_VERSION to 3.1.4. The NEXT_RUBY_VERSION variable might not be required, depending if the 2nd and 3rd steps in gitlab-org&11659 (closed) are checkmarked. Check with @balasankarc to confirm.
  • Notify Slack channels #development, #backend, #frontend and #staging-ref that the deployment has started.
  • Notify @igor.drozdov, @mkaeppler and @niskhakova when the deployment is done so they can proceed with Monitor second experimental Ruby 3.1 package roll out to staging.

Continue auto deploys

  • Allow the package to bake for 1 hour on gprd-cny.
  • Once a new package is deployed to gstg-cny and gstg-ref and gprd-cny, notify the Slack channels that the Ruby 3.1 package is no longer on those environments.

Key metrics to observe

Edited by Reuben Pereira