Fix bug in remote.feature
Dropping 1.8.7 support, adding 2.0.0
Resolve failing TravisCI build

- for 1.8.7
Revert "Resolve failing TravisCI build"

This reverts commit 8787bd8a22d118e2cf863a01e77fe8f43479b2c5.

Dropping support for 1.8.7, for real this time
Remove API MOCK code from stage.rb

- Use dependency injection insead
- Add a Factory class for testing
Movie #auth_token and Toolbelt sh into API class

- refactoring is FUN
Rescue from no toolbelt
And THIS is why we test
Fix issues with running Ruby 2.0.0 and using Heroku Toolbelt

The issue was that bundle sets ENV['RUBYOPT'] after it has been
loaded, which causes any subprocesses that get spawned
to be confused. If you spawn the processes using the incantation
"Bundler.with_clean_env", the RUBYOPT will be temporarily restored.

See for more info:
http://pivotallabs.com/service-oriented-foreman/

We wrote a cucumber test (shell_execution.feature) that exposes
the problem, but it requires that you have the Heroku Toolbelt
installed (not the gem) as well as RVM and Ruby 2.0.
Merge pull request #155 from tjgrathwell/fix-for-ruby-2

Fix issues with running Ruby 2.0.0 and using Heroku Toolbelt
Allow integration tests to run on Travis

- Use addons that do not require verification
- Add cucumber and travis tasks
Update dependencies for Travis
More Travis updates

- Upgrade RSpec
- Configure git user
Restrict testing to Rails 3.2
More Travis updates

- Disable strict host checking
- Check the environment
- Lock down rails to 3.2.7
- Add pg
Travis updates

- parameterize ruby version in Gemfile creation
- create and add deploy key
Add blank password setting to ssh-keygen
s/install/before_install/
Clean up keys after builds
TRAVIS_BUILD_ID is not unique enough. Use JOB_NUMBER instead