Coordinate deployment of ci_builds.id bigint db migration
We have an MR pending for finalizing the swap of bigint on the ci_builds.id table. As this is a post migration with some associated risks we want to deploy it in isolation without any other changes (to make debugging of problems easier and as we wouldn't be able to roll back if other changes would introduce regressions).
The database team will get in contact with us before merging the MR. We then should do the following:
-
Determine the DRI from the database team and coordinate the time for merging -
Deactivate auto-deploy tasks with /chatops run auto_deploy pause
-
merge the MR and set labels pick into autodeploy
andseverity::2
, -
Manually trigger auto_deploy:pick
schedule. You might want to check this is the only MR with~Pick into auto-deploy
here -
Enable https://ops.gitlab.net/gitlab-org/release/tools/-/feature_flags/191/edit -
Manually trigger auto_deploy:tag
schedule -
Disable https://ops.gitlab.net/gitlab-org/release/tools/-/feature_flags/191/edit -
Once the new coordinated pipeline has been created and the tests of the merged MR are green on the autodeploy branch enable auto-deploy tasks with /chatops run auto_deploy unpause
-
make sure that the last coordinated pipeline before the one containing the migration MR is making it into gprd, so that we don't have any other undeployed changes -
inform the EOC and the database team about the coordinated pipeline deploying the post migration -
watch the coordinated pipeline and especially the post-migration - ping database team on problems
/cc @gitlab-org/release/managers @ggillies @rpereira2
Edited by Robert Speicher