Replace 'rbx-2' with 'rbx'. #740
Conversation
Rubinius no longer supports any version of the 2.x epoch. Use of 'rbx' is encouraged so that the current stable release is tested. Rubinius releases as frequently as once or more a day and any attempt to 'lock' to a Rubinius version significantly disadvantages a project by not using Rubinius fixes and enhancements. It also disadvantages Rubinius because time is wasted dealing with outdated issues for which fixes have already been released.
|
Do these instructions work for the default travis environment? (Doesn't rubinius require "dist: trusty" too?) |
|
@iainbeeston that's a good point. They could work on Precise if Travis pre-installs the required libraries to make LLVM > 3.5 available. Otherwise, I have not been able to build Rubinius binaries for Precise that will statically link the required libc++ and supporting libraries. Precise will EOL in a short few months, and given the time it's taken for Trusty to be the default, the process cannot start soon enough. So perhaps this could be an impetus for that. I'd be open to adding caveats on Rubinius requiring Trusty if that's desirable. |
user/languages/ruby.md
Outdated
| @@ -55,7 +55,7 @@ If you don't specify a version, Travis CI will use MRI 1.9.3 as the default. | |||
|
|
|||
| When using Rubinius, there's currently an issue with selecting the correct version | |||
| in RVM in our build environment, but only when specifying `rbx` as your version. As | |||
| a workaround, specify `rbx-2` instead. | |||
| a workaround, specify `rbx` instead. | |||
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
Per a discussion on travis-ci/docs-travis-ci-com#740, using Ubuntu Trusty instead might resolve the rbx issue. It also confirms that using `rbx` instead of `rbx-2` is the correct thing to do.
There don’t seem to binary versions of rbx-2 available on Travis any more, so switch to using `rbx` instead. Per travis-ci/docs-travis-ci-com#740, this seems to be the correct thing to do. However, the `rbx` build is still failing. This seems like it might be a temporary build environment issue, so allow the rbx build to fail until it is resolved.
|
These instructions currently aren't working for us on |
|
@pnomolos yep, there's a bug in RVM that has been long-standing (years) and intermittent. You can see our Travis Canary results here https://travis-ci.org/rubinius/travis-canary/builds/163446822 |
|
@brixen Has any though been given to moving from RVM over to something like rbenv? Maybe ref: rbenv/ruby-build#42 (comment) |
|
Closing this as the issue seems fixed by #1534 |
Rubinius no longer supports any version of the 2.x epoch. Use of 'rbx' is
encouraged so that the current stable release is tested.
Rubinius releases as frequently as once or more a day and any attempt to
'lock' to a Rubinius version significantly disadvantages a project by not
using Rubinius fixes and enhancements.
It also disadvantages Rubinius because time is wasted dealing with outdated
issues for which fixes have already been released.