Skip to content

Commit

Permalink
Update 'Building Ruby' docs with another fix for Bundler 2.0
Browse files Browse the repository at this point in the history
I discovered this was necessary after upgrading to Bundler 2.1.0 yesterday,
only for CI to break when 2.1.1 came out today.

See also: faker-ruby/faker#1867
  • Loading branch information
connorshea committed Dec 18, 2019
1 parent c004010 commit 29a137b
Showing 1 changed file with 20 additions and 0 deletions.
20 changes: 20 additions & 0 deletions user/languages/ruby.md
Original file line number Diff line number Diff line change
Expand Up @@ -167,6 +167,26 @@ want to use Bundler 2.0, try one of the following solutions:
```
{: data-file=".travis.yml"}


* If you're using a version of Ruby before 2.6 and want to use Bundler 2.x,
you'll also want to make sure to upgrade to a newer version of RubyGems.
On the default version of RubyGems shipped with older versions of Ruby, the
Bundler version in `Gemfile.lock` must match exactly the version being used,
or it will error. This would cause when a new version of Bundler comes out,
but it's fixed in more recent RubyGems releaeses.

```yaml
before_install:
- yes | gem update --system --force`
- gem install bundler
```
{: data-file=".travis.yml"}
It's necessary to pipe `yes` into the `gem update --system` command because
of a separate issue involving older versions of RubyGems shipping with a bad
binstub, which prompts interactive confirmation from the user.


* If you are using Ruby 2.3.x but wish to explicitly stay on Bundler 1.x (e.g., for dependency
reasons such as Rails 4.2.x), write:

Expand Down

0 comments on commit 29a137b

Please sign in to comment.