Rollback to a set version instead of an arbitrary number of steps

The previously hard-coded value can fail when new migrations are introduced since multiple migrations may need to be rolled back atomically. Closes #40302

Rollback to a set version instead of an arbitrary number of steps
e06f678c · Stan Hu · be0ce05c · e06f678c
Commit e06f678c authored Mar 22, 2018 by Stan Hu
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

.gitlab-ci.yml .gitlab-ci.yml +1 -1

No files found.
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -544,7 +544,7 @@ migration:path-mysql:
 .db-rollback: &db-rollback
  <<: *dedicated-no-docs-pull-cache-job
  script:
-    - bundle exec rake db:rollback STEP=119
+    - bundle exec rake db:migrate VERSION=20170523121229
    - bundle exec rake db:migrate

 db:rollback-pg: