Commit 685b0056 authored by Stan Hu's avatar Stan Hu

Workaround for Geo DB init failure by explicitly skipping the post-migrations

parent 2cb19720
...@@ -27,7 +27,7 @@ before_script: ...@@ -27,7 +27,7 @@ before_script:
- '[ "$USE_BUNDLE_INSTALL" != "true" ] || retry bundle install --without postgres production --jobs $(nproc) $FLAGS' - '[ "$USE_BUNDLE_INSTALL" != "true" ] || retry bundle install --without postgres production --jobs $(nproc) $FLAGS'
- retry gem install knapsack - retry gem install knapsack
- '[ "$SETUP_DB" != "true" ] || bundle exec rake db:drop db:create db:schema:load db:migrate add_limits_mysql' - '[ "$SETUP_DB" != "true" ] || bundle exec rake db:drop db:create db:schema:load db:migrate add_limits_mysql'
- '[ "$SETUP_DB" != "true" ] || bundle exec rake geo:db:drop geo:db:create geo:db:schema:load geo:db:migrate' - '[ "$SETUP_DB" != "true" ] || SKIP_POST_DEPLOYMENT_MIGRATIONS=1 bundle exec rake geo:db:drop geo:db:create geo:db:schema:load geo:db:migrate'
stages: stages:
- prepare - prepare
......
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