Permalink
Browse files

Add .travis.yml

In support of rubinius/rubinius#2006 let's get this working on Travis.
  • Loading branch information...
jc00ke committed Nov 12, 2012
1 parent 5cef5fc commit ea05088501bbc793546b37d8f470beb7d05a0c3a
Showing with 9 additions and 0 deletions.
  1. +9 −0 .travis.yml
View
@@ -0,0 +1,9 @@
+before_script:
+ - gem install test-unit
+ - rake build
+
+rvm:
+ - 1.8.7
+ - 1.9.3
+ - rbx-18mode
+ - rbx-19mode

5 comments on commit ea05088

@djberg96

This comment has been minimized.

Show comment Hide comment
@djberg96

djberg96 Nov 13, 2012

Is the .travis.yml file a standard to include in gems now? I mean, will this be beneficial outside of Rubinius?

Is the .travis.yml file a standard to include in gems now? I mean, will this be beneficial outside of Rubinius?

@jc00ke

This comment has been minimized.

Show comment Hide comment
@jc00ke

jc00ke Nov 13, 2012

Owner

It's becoming standard, and it is beneficial to all of the Ruby implementations, not just Rubinius.

It's a good way to communicate the status of your library.

We on the Rubinius project are trying to support as many gems with C-ext as possible. Travis is a great way to help us coordinate that.

Owner

jc00ke replied Nov 13, 2012

It's becoming standard, and it is beneficial to all of the Ruby implementations, not just Rubinius.

It's a good way to communicate the status of your library.

We on the Rubinius project are trying to support as many gems with C-ext as possible. Travis is a great way to help us coordinate that.

@jc00ke

This comment has been minimized.

Show comment Hide comment
@jc00ke

jc00ke Nov 13, 2012

Owner

Yes, it's becoming the standard, as it communicates the status of your library to anyone that wants to use it.

It's definitely beneficial to all of the implementations, not just Rubinius.

We on the Rubinius team are trying to find libraries with C-extensions that can be tested against Rubinius to ferret out anything we may have missed or need to support.

Owner

jc00ke replied Nov 13, 2012

Yes, it's becoming the standard, as it communicates the status of your library to anyone that wants to use it.

It's definitely beneficial to all of the implementations, not just Rubinius.

We on the Rubinius team are trying to find libraries with C-extensions that can be tested against Rubinius to ferret out anything we may have missed or need to support.

@jc00ke

This comment has been minimized.

Show comment Hide comment
@jc00ke

jc00ke Nov 13, 2012

Owner

Yes, it's becoming the standard, as it communicates the status of your library to anyone that wants to use it.

It's definitely beneficial to all of the implementations, not just Rubinius.

We on the Rubinius team are trying to find libraries with C-extensions that can be tested against Rubinius to ferret out anything we may have missed or need to support.

Owner

jc00ke replied Nov 13, 2012

Yes, it's becoming the standard, as it communicates the status of your library to anyone that wants to use it.

It's definitely beneficial to all of the implementations, not just Rubinius.

We on the Rubinius team are trying to find libraries with C-extensions that can be tested against Rubinius to ferret out anything we may have missed or need to support.

@jc00ke

This comment has been minimized.

Show comment Hide comment
@jc00ke

jc00ke Nov 13, 2012

Owner
Owner

jc00ke replied Nov 13, 2012

Please sign in to comment.