Skip to content

Commit

Permalink
Use explicit gemfile in bundle exec in CI build
Browse files Browse the repository at this point in the history
These calls to `bundle exec` all come after a call to `bundle install
--gemfile=xxx` and the latter will only take effect if we use `bundle
exec --gemfile=xxx` (or if the `BUNDLE_GEMFILE` is set).

In practice all these cases are using the default `Gemfile`, so these
changes don't actually have any effect. However, I think making things
explicit makes the code easier to follow.
  • Loading branch information
floehopper committed Dec 24, 2024
1 parent 2b05e09 commit c30c658
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions .circleci/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ jobs:
condition:
equal: [ "Gemfile", << parameters.gemfile >>]
steps:
- run: bundle exec rake test
- run: bundle exec --gemfile=<< parameters.gemfile >> rake test
- when:
condition:
matches:
Expand All @@ -48,7 +48,7 @@ jobs:
- equal: [ "ruby:latest", << parameters.docker-image >> ]
- equal: [ "Gemfile", << parameters.gemfile >>]
steps:
- run: bundle exec rake test:performance
- run: bundle exec --gemfile=<< parameters.gemfile >> rake test:performance
- run: MOCHA_GENERATE_DOCS=1 bundle install --gemfile=<< parameters.gemfile >>
- run: MOCHA_GENERATE_DOCS=1 rake yardoc
lint:
Expand All @@ -60,7 +60,7 @@ jobs:
- run: gem --version
- run: bundle --version
- run: bundle install --gemfile=Gemfile
- run: bundle exec rake lint
- run: bundle exec --gemfile=Gemfile rake lint

workflows:
build-all:
Expand Down

0 comments on commit c30c658

Please sign in to comment.