Commit e06f678c authored by Stan Hu's avatar Stan Hu

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
parent be0ce05c
...@@ -544,7 +544,7 @@ migration:path-mysql: ...@@ -544,7 +544,7 @@ migration:path-mysql:
.db-rollback: &db-rollback .db-rollback: &db-rollback
<<: *dedicated-no-docs-pull-cache-job <<: *dedicated-no-docs-pull-cache-job
script: script:
- bundle exec rake db:rollback STEP=119 - bundle exec rake db:migrate VERSION=20170523121229
- bundle exec rake db:migrate - bundle exec rake db:migrate
db:rollback-pg: db:rollback-pg:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment