Move all jruby travis builds to allow_failures section#5112
Conversation
deivid-rodriguez
left a comment
There was a problem hiding this comment.
I think at this point you can just say rmv: jruby-9.1.12.0 under allowed_failures. You don't need to specify every gemfile.
|
@deivid-rodriguez cool, I just made that change but I don't see any builds for jruby so it means its not running them at all since it doesn't know what Gemfile to use. You can see that here: https://travis-ci.org/activeadmin/activeadmin/builds/258772337 I'll delete the second commit. In fact it wasn't showing up for the previous change either. I don't think it'll run it to begin with if its all in the |
bdf5837 to
6a8b1c3
Compare
| - bundle exec rake docs:build | ||
|
|
||
| rvm: | ||
| - jruby-9.1.12.0 |
There was a problem hiding this comment.
You need to restore this entry I think. Otherwise it won't run any jruby build, indeed.
6a8b1c3 to
f38f5ff
Compare
|
I pushed this through as it appears Travis moved us to Trusty and broke the build for JRuby. There may be other fixes available but this was simplest. |
As we discussed that we'd move this to the
allow_failuressection. I just had another travis failure because the jruby rails42 build is failing in #5081. 😩 Sorry @deivid-rodriguez. 😞