This project is archived and is in readonly mode.
RVM support in CI
Reported by Cezary Baginski | May 7th, 2010 @ 11:43 AM | in 3.x
I created a non-intrusive patch to allow CI to use rvm for selecting and using Ruby versions.
Problems solved
- CI now can use a recommended ruby version instead of the possibly broken one installed
- sudo is no longer required
- rvm is installed if necessary
- supplied ruby version is installed if necessary
- backward compatible with existing CI setups
- with a rvm-patched ruby_source_code gem (e.g. my fork at http://github.com/e2/ruby_core_source), ruby-debug1.9 can now be installed with any ruby revision
- fixed missing CI=1 for bundler commands
- isolated CI's on same machine with different rubies and their gems
- takes some of the burden out of configuring a CI
BONUS
- should fix the broken CI 1.9 build on ci.rubyonrails.org
- should solve some ruby/gem problems with default Ubuntu Ruby versions
How to run
rake ci
or see summary in ci/rvm_helper.rb
All feedback is more than welcome :)
Comments and changes to this ticket
-
Cezary Baginski May 7th, 2010 @ 11:56 AM
Rebased against master.
Notes:
- some commands with progress may need silencing
- i18n in 1.9 spits out too many warnings: fixed in my fork: http://github.com/e2/i18n
- requires curl (heck, what doesn't nowadays ...)
- I use 1.9.1-head in the helper script - this may not be what people want
- additional deps may be required in the Gemfile - I think rdoc was missing from the installed gems
Happy CI'ing!
-
Santiago Pastorino February 2nd, 2011 @ 05:02 PM
- State changed from new to open
- Tag changed from 1.9, ci, patch, tests to 19, ci, patch, tests
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
Santiago Pastorino February 2nd, 2011 @ 05:02 PM
- State changed from open to stale
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>