Create method for Release Managers to tag new Deployment pipeline without picking or preparing new auto deploy branch
Summary
For the Ruby 3.1 rollout, there will be no changes required to the Rails project (gitlab-org/gitlab
). So there will be no commit to pick into auto deploy.
Instead, we will need to set environment variables (will be defined in #19712 (closed)) that will tell Omnibus and CNG to prepare a package that contains Ruby 3.1.
We need a way to create a new Coordinator pipeline without creating a new auto deploy branch or picking into auto deploy, since we want a deployment pipeline that only contains the Ruby 3.1 upgrade, and no other changes.
Proposal
-
Add a new force_tag
parameter toTasks::AutoDeploy::Tag
and use it at auto_deploy/tag.rb#L23 to force tag when the parameter is set totrue
. -
Create a rake task that triggers the Tasks::AutoDeploy::Tag
class withforce_tag
set to true. -
Create a CI job that triggers the above rake task. -
Create an inactive scheduled job that can be used to trigger the above CI job.