Use a Keep to perform migration squash automatically
Overview
The gitlab-housekeeper
can be used to automatically create MRs for routine maintenance. See the README.md
to understand how to contribute.
We can add a new keep to https://gitlab.com/gitlab-org/gitlab/-/tree/master/keeps which automates the migration squashing process. We can use the migration milestone to squash migrations through a required stop -1 release, E.G: 16.3
, 16.7
, 16.11
are required stops, current version is 17.0
, squash up to 16.7
.
Desired outcome
-
Squash migrations with assigned milestones. -
- Migrations before 16.6 don't have a specified milestone. It makes sense to wait until we squash all migrations up to 16.5.
-
Include an assignee to Housekeeper change -
- Housekeeper currently doesn't support adding an MR assignee. It will be necessary to assign someone from the DB team to finish the squash.
-
Create a keep that will use the migration milestone to perform the squash. -
- Based on the current version, squash all migrations until -1 version from the current release. E.G:
16.3
,16.7
,16.11
are required stops, current version is17.0
, squash up to16.7
.
- Based on the current version, squash all migrations until -1 version from the current release. E.G:
-
- MR failures are acceptable, they will be fixed by the assignee — some specs may fail due to the removal of some migrations.
Edited by Leonardo da Rosa