This repository has been archived by the owner on Jun 30, 2022. It is now read-only.
adding ruby versions to the travis.yml. #117
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
I think we should support multiple versions of ruby in case users have reasons for 2.0 v. 2.1 v. 2.2 so I added the stable builds from each of these in the travis configs so that the test suite will run against all of these.
|
This is a good idea! Is 2.0.0 the latest patch release of 2.0.x? |
|
Yes, I picked the latest stable releases from each of the 2.x series per ruby's website: https://www.ruby-lang.org/en/downloads/ |
jimmycuadra
added a commit
that referenced
this pull request
Jun 10, 2015
adding ruby versions to the travis.yml.
|
FYI, if you do: TravisCI will automatically build using the latest release of each major Ruby version (So right now it'd be "2.0" -> "2.0.0", "2.1" -> "2.1.6", etc). Want a PR to switch? (Throwing "cache: bundler" in there would also help a bit.) |
|
@esigler Yes, please! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I think we should support multiple versions of ruby in case users have reasons
for 2.0 v. 2.1 v. 2.2 so I added the stable builds from each of these in the
travis configs so that the test suite will run against all of these.
If you only want to test against 2.0 that's fine, just close this. If you want to test against multiple versions of ruby then merge away!