Unlock Bundler version for testing #1009
Merged
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
marcotc
added
dev/testing
marcotc
force-pushed
the
ci/unlock-bundler
branch
from
2ba493b
to
e56be04
Compare
|
CI 2.7 build still looks like it has a Bundler issue, this time when running Grape tests? |
|
Thank you for the tip @delner, I addressed the issue (CI had a bad cache gemset from another build, starting a clean rebuild job fixed it). |
delner
approved these changes
Apr 20, 2020
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.
The version of bundler we use for testing in CircleCI was locked for Ruby 2.7 due to a bug which seemed to be related to the Appraisal gem.
That issue was addressed in the upstream ruby docker image, so new docker images we build for CI will work correctly with new versions of bundler.
This PR unlocks the version of bundler so we can continue testing with the latest available version. One thing to note is that the version of bundler we use in CI is locked at the time we publish the image, so we are not actually constantly upgrading bundler. This PR then publishes a new version of the Ruby 2.7 CI image, to allow it to upgrade to the latest version.