Skip to content

Reschedule migration related to remediation

Zamir Martins requested to merge reschedule_migration_for_remediation into master

What does this MR do and why?

Reschedule migration related to remediation.

Original migration: !109397 (merged)

Related issue: https://gitlab.com/gitlab-org/gitlab/-/issues/239183

DB migrate

bundle exec rails db:migrate
main: == 20230313150531 RescheduleMigrationForRemediation: migrating ================
main: == 20230313150531 RescheduleMigrationForRemediation: migrated (0.0674s) =======

ci: == 20230313150531 RescheduleMigrationForRemediation: migrating ================
ci: -- The migration is skipped since it modifies the schemas: [:gitlab_main].
ci: -- This database can only apply migrations in one of the following schemas: [:gitlab_ci, :gitlab_shared, :gitlab_internal].
ci: == 20230313150531 RescheduleMigrationForRemediation: migrated (0.0072s) =======

bundle exec rails db:migrate:down:main VERSION=20230313150531
main: == 20230313150531 RescheduleMigrationForRemediation: reverting ================
main: == 20230313150531 RescheduleMigrationForRemediation: reverted (0.0302s) =======

Query plan & queries

DB testing job results

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Zamir Martins

Merge request reports

Loading