Analyse GitLab upgrade process, test coverage and reporting
The issue is to get familiar with the current state of GitLab upgrade testing. Specifically for minor and major upgrades.
-
Analyse the current coverage -
Document the current findings above to a handbook page -
Explore differences between various migration types: post-deploy, background, pre - moved to #1846
Migration related notes
> post-migrations shouldn't contain schema changes critical for the application to work. These are limited to data migrations, background migrations, or DDL operations that are not strictly required for the application to operate (e.g. adding/removing indexes)To perform a zero-downtime upgrade it's expected for self-managed to run post-deploy migrations when updating to a newer version. However, it's not uncommon for self-managed to skip these from time to time, when this happens they are referred to the zero-downtime upgrade doc or to version-specific upgrading instructions.
https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5494#note_1276985355
Edited by Nailia Iskhakova