Need to identify target Rubies #7

Open
jredville opened this Issue May 10, 2012 · 3 comments

Projects

None yet

2 participants

@jredville
Collaborator

rake spec:portability prepares every Ruby installed on the system, but it doesn't enforce the existence of a set of Ruby's. We should probably enforce the existence of at least Ruby 1.9, JRuby and RBX, but I could use input on the versions required and any other targets.

@rtlong
Collaborator
rtlong commented May 10, 2012

I had actually considered setting it up on TravisCI, since it's where all the "cool kids" hang out. :-) ...and because it's awesome, and super easy. They'll test it across the board. I suppose we should find out which Rubies guard tests against then which Rubies Resque tests against, and set guard-resque to the intersection of those sets.

@jredville
Collaborator

Guard:

rvm:
  - 1.8.7
  - 1.9.2
  - 1.9.3
  - ruby-head
  - ree
  # - jruby-18mode
  # - jruby-19mode
  # - jruby-head
  - rbx-18mode
  - rbx-19mode

Resque:

rvm:
  - 1.8.7
  - 1.9.2
  - 1.9.3
  - jruby-18mode
  - jruby-19mode
  - rbx-18mode
  - rbx-19mode

So that implies we should run against:

rvm:
  - 1.8.7
  - 1.9.2
  - 1.9.3
  - rbx-18mode
  - rbx-19mode

However, from looking at guard's readme, I don't know why they are not running jruby in Travis. Unless there are objections, I can set this up, starting with the above list, and then seeing if adding jruby causes failures. Should I include everyone in the notification list at this point?

@jredville jredville closed this Jun 7, 2012
@jredville jredville reopened this Jun 7, 2012
@jredville
Collaborator

Sorry, hit the wrong button

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment