Skip to content
This repository has been archived by the owner on Feb 7, 2018. It is now read-only.

Commit

Permalink
Update Travis CI configuration
Browse files Browse the repository at this point in the history
  • Loading branch information
@sikachu
sikachu committed Feb 3, 2012
1 parent 4183c89 commit 4eb18d2
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions .travis.yml
View file
Expand Up @@ -2,7 +2,7 @@ rvm:
- 1.8.7
- 1.9.2
- 1.9.3
- rbx
- rbx-2.0
- rbx-18mode
- rbx-19mode
- ree
- jruby

3 comments on commit 4eb18d2

@michaelklishin
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

by the way, there are now jruby-18mode and jruby-19mode as well as jruby-head (which now defaults to 1.9 mode per JRuby team decision)

@sikachu
Copy link
Contributor Author

@sikachu sikachu commented on 4eb18d2 Feb 3, 2012

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome. Do you think I should test against ruby-head as well, or do people only use released version?

@michaelklishin
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is your (team) choice. Most people don't test against ruby-head but I'd not say it is uncommon to do so. There are usually no issues with it unless something really has changed in the core library, standard library and so on. For a relatively small library like Cocaine that does not have dozens of dependencies or native parts, testing against ruby-head probably will be a breeze. Try it ;)

Please sign in to comment.