Ensure rake is called within the correct bundle context

This commit is contained in:
Luke "Jared" Bennett 2017-01-30 16:46:37 +00:00
parent d6450bb249
commit 8c5d55ea33
1 changed files with 4 additions and 4 deletions

View File

@ -271,7 +271,7 @@ rake db:migrate:reset:
<<: *use-db
<<: *dedicated-runner
script:
- rake db:migrate:reset
- bundle exec rake db:migrate:reset
rake db:seed_fu:
stage: test
@ -302,7 +302,7 @@ teaspoon:
script:
- npm install
- npm link istanbul
- rake teaspoon
- bundle exec rake teaspoon
artifacts:
name: coverage-javascript
expire_in: 31d
@ -353,10 +353,10 @@ migration paths:
- cp config/resque.yml.example config/resque.yml
- sed -i 's/localhost/redis/g' config/resque.yml
- bundle install --without postgres production --jobs $(nproc) $FLAGS --retry=3
- rake db:drop db:create db:schema:load db:seed_fu
- bundle exec rake db:drop db:create db:schema:load db:seed_fu
- git checkout $CI_BUILD_REF
- source scripts/prepare_build.sh
- rake db:migrate
- bundle exec rake db:migrate
coverage:
stage: post-test