Question

In the rails project I’m working on I inserted support for rspec, cucumber and autotest with this Gemfile (partial)

gem 'rspec-rails'
gem 'cucumber-rails'
gem 'autotest-standalone'
gem 'autotest-rails-pure'
gem 'zentest-without-autotest'

however in order to run tests with autotest i need to execute bundle exec autotest otherwise it fails with this message

$ autotest 
loading autotest/cucumber_rails_rspec_rspec2
Error loading Autotest style autotest/cucumber_rails_rspec_rspec2 (no such file to load -- autotest/cucumber_rails_rspec_rspec2). Aborting.

Now I’m developing on a Mac and I’d like to enable autotest-growl and autotest-fsevents gem, but if I insert those lines in my ~/.autotest

require 'autotest/growl'
require 'autotest/fsevent'

then I need to insert the corresponding gems in the Gemfile and everything works, but it breaks builds on my CI server (which is on Linux)

How to solve this without maintaining a different Gemfile for local and CI environments?

EDIT:

For the moment I solved with these lines in Gemfile

if RUBY_PLATFORM.downcase.include?("darwin") # I'm on Mac
  gem 'autotest-fsevent'
  gem 'autotest-growl'
end

It works both locally and on the CI server, I don’t know if it mess something, for the moment it seems to work flawlessly.

Any cleaner way to do that is still welcome.

EDIT2:

I switched to groups solutions. While the previous monkeypatch works pretty well both in development and for continuous integration, it will gives you an error in production if you use capistrano bundler tasks for deployments or if you use bundle install --deployment option (which is advised in production)

When using the if RUBY_PLATFORM.downcase.include?("darwin") line you’ll get this error on deploy.

# bundle install --deployment --without development test
You are trying to install in deployment mode after changing
your Gemfile. Run `bundle install` elsewhere and add the
updated Gemfile.lock to version control.

You have deleted from the Gemfile:
* autotest-fsevent
* autotest-growl

So my final solution to this problem is to include platform specific gems in a given group, say osx, and then in production and on CI server exclude it using bundle.

If you use capistrano to deploy put this in your config.rb

set :bundle_without,  [:development, :test, :osx]
# capistrano bundler task
require "bundler/capistrano"

Answer 1

You might want to use groups in your gemfile, something like:

group :development do
  gem "autotest-growl"
  gem "autotest-fsevents"
end

and on the server you use: $ bundle install --without development