Skip to content

Conversation

@mtsmfm
Copy link
Contributor

@mtsmfm mtsmfm commented Apr 25, 2016

context: #1699 (comment)

Path for JRuby is not correct so tests run on CRuby 1.9 till now...

@NullVoxPopuli
Copy link
Contributor

It's funny how many times we need to fix things just to get appveyor happy.. :-\

Path for JRuby is not correct so tests run on CRuby 1.9 till now...
@mtsmfm mtsmfm force-pushed the fix-appveyor-setting-for-jruby branch from c3275f3 to d9eac2a Compare April 25, 2016 00:25
@beauby
Copy link
Contributor

beauby commented Apr 25, 2016

LGTM, I'll merge unless @bf4 has concerns 🎉

- ruby_version: "jruby-9.0.4.0"
- ruby_version: "Ruby21"
- ruby_version: "Ruby21-x64"
- ruby_version: "jruby-9.0.0.0"
Copy link
Member

Choose a reason for hiding this comment

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

why are we lowering the Jruby version? and putting the JRUBY_OPTS globally?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Only available jruby-9.0.0.0 on appveyor:
https://ci.appveyor.com/project/mtsmfm/active-model-serializers/build/1

putting the JRUBY_OPTS globally?

Yeah, I went same way for travis but it is not smart 😕

https://github.com/rails-api/active_model_serializers/blob/master/.travis.yml#L25-L26

Should I apply patch for that on this PR or create another PR?

@bf4
Copy link
Member

bf4 commented Apr 25, 2016

I have questions, but am ok merging to that we can get green and then revisit

@beauby beauby merged commit 0165215 into rails-api:master Apr 25, 2016
@mtsmfm mtsmfm deleted the fix-appveyor-setting-for-jruby branch April 26, 2016 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants