summaryrefslogtreecommitdiff
path: root/db/migrate/20180201145907_migrate_remaining_issues_closed_at.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add version 4.2 to all existing migrationsjprovazn-versioned-migrationsJan Provaznik2018-11-221-1/+1
| | | | | | | | | DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
* Enable rubocop for db/**/* and ee/db/**/*49582-enable-cops-for-dbLin Jen-Shin2018-07-251-0/+1
|
* Handle EE edge cases in issues.closed_at migrationbetter-issues-closed-at-cleanupYorick Peterse2018-02-051-3/+16
| | | | | | | | | EE seems to have had an outdated schema at some point, leading to some environments not having the right columns in place. This adjusts the migration for `issues.closed_at` so it takes care of those cases, ensuring data can be migrated properly. Fixes https://gitlab.com/gitlab-org/gitlab-ee/issues/4803
* Finish any remaining jobs for issues.closed_atissues-closed-at-stealYorick Peterse2018-02-011-0/+42
In the event of Sidekiq jobs getting lost there may be some rows left to migrate. This migration ensures any remaining jobs are completed and that all data has been migrated. This fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/41595