This repository was archived by the owner on Mar 7, 2018. It is now read-only.
Update travis config to current ruby versions.#683
Merged
Conversation
This has the nice side effect of fixing the failing travis builds. :-) The build failures seen with older ruby versions (for example on 1.9.3) seem to be due to the following bundler bug: rubygems/bundler#3558
Contributor
Author
|
@tylermauthe, @pushmatrix This is a pretty simple one, can we get this merged? |
Contributor
|
Looks good to me 👍 Thanks a lot! |
Member
|
Of course! Thanks @qbrossard ! |
pushmatrix
added a commit
that referenced
this pull request
Feb 16, 2016
Update travis config to current ruby versions.
This file contains hidden or 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
This has the nice side effect of fixing the failing travis builds. :-)
The build failures seen with older ruby versions (for example on 1.9.3) seem to be due to the following bundler bug:
rubygems/bundler#3558
fixes #682