Remove semver usage
Describe in detail what your merge request does and why.
This MR removes the usage of the recently introduced (%15.1) semver
field in Ci::Runner
, as we decided to change the approach. Therefore we're stopping the BackfillCiRunnerSemver
background migration which was introduced in %15.2 (therefore executed only in GitLab.com) by following the recommended approach in https://docs.gitlab.com/ee/development/database/deleting_migrations.html. The semver
field and related indices will be removed in a future milestone.
MRs being reverted: !89024 (merged), !89054 (merged)
Part of GraphQL: Expose filter on GitLab Runner upgrade... (#358406 - closed)
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Migrations
Migrate up
ci: == 20220624062300 DeleteBackfillCiRunnerSemverMigration: migrating ============
ci: == 20220624062300 DeleteBackfillCiRunnerSemverMigration: migrated (0.0107s) ===
Migrate down
ci: == 20220624062300 DeleteBackfillCiRunnerSemverMigration: reverting ============
ci: == 20220624062300 DeleteBackfillCiRunnerSemverMigration: reverted (0.0017s) ===
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.