.travis.yml

language: objective-c
env:
  # This is what 10.8.x comes with and we want to support that.
  - RVM_RUBY_VERSION=system NOEXEC_DISABLE=1 RUBY_VERSION_SPECIFIC='sudo gem update --system && sudo gem install bundler --no-ri --no-rdoc'
  - RVM_RUBY_VERSION=1.9.3 NOEXEC_DISABLE=1 RUBY_VERSION_SPECIFIC='sudo ln -s /usr/bin/llvm-gcc-4.2 /usr/bin/gcc-4.2 && curl http://curl.haxx.se/ca/cacert.pem -o /usr/local/share/cacert.pem' SSL_CERT_FILE=/usr/local/share/cacert.pem
before_install: source ~/.rvm/scripts/rvm && rvm use $RVM_RUBY_VERSION
install: eval $RUBY_VERSION_SPECIFIC && rake bootstrap
script: bundle exec rake spec:ci

gistfile1.md

The nice thing about having a real OS X installation is that I can run the test suite against that too and be ensured that I did not break anything for others while developing on a faster newer Ruby myself. Therefore, it would be great if the system Ruby gets some love in the form of:

• Pre-installed Bundler. Even though it’s not part of a normal system installation, a lot of projects will need it to run their test suites, even Objective-C projects. E.g. libPusher.
• Updated RubyGems, which is needed to install the latest Bundler.

The pre-installed (with RVM) Ruby 1.9.3 version has a couple of issues:

• The RVM version installed is outdated (I think) and does not support the --fuzzy flag etc.
• I need to source ~/.rvm/scripts/rvm myself, otherwise I get: RVM is not a function, selecting rubies with 'rvm use ...' will not work.. This probably means the profile of the user running the build is missing the required RVM setup.
• I need to configure OpenSSL to use a valid root CA file, as described in this comment, otherwise it won’t be able to verify connections.
• I need to symlink /usr/bin/gcc-4.2 to /usr/bin/llvm-gcc-4.2, otherwise this happens. Note that this not a RVM issue perse, it will probably occur while installing other tools as well.

Oops, didn’t see the newer messages.

@henrikhodne That list sounds excellent.

Regarding the LLVM issue, it’s true that older Rubies will have problems, but since 1.9.3-p125 it should work (see the release notes: http://www.ruby-lang.org/en/news/2012/02/16/ruby-1-9-3-p125-is-released/).

/cc @mpapis