Correctly set ENV['BUNDLE_BIN_PATH'] #2285
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Below is only when using ruby 2.7.
This fixes CI failures that occur with nested
bundle execcommands, as often testing is started withbundle exec <test>...Once activated, bundler redefines
Gem.activate_bin_path, and the value ofENV['BUNDLE_BIN_PATH']is used for subsequent bundle commands.In master/trunk/2.7.0, bundler is installed as a default gem, and at some point in time I assume the bundle exe folder was within the lib/bundler folder. Now, it is in the gems folder. Patch updates the location so that that
ENV['BUNDLE_BIN_PATH']is correct.ping @hsbt