Continuous Integration for Ruby on Rails? [closed]

Answer 1

Check out Tddium. Tddium support continuous integration, deployment and interactive testing of Ruby applications. It provides a managed environment with support for Selenium, Headless Webkit, and Solr. It hosts live Postgres, MySQL, Mongo, and Redis instances. And it automatically parallelizes large test suites.

Answer 2

Updated Feb-2015

Codeship

There was a lack of development on Drone.io so I switched to Codeship and I'm thoroughly enjoying it. It's actively developed and improved, has great design and is very fast. Plus, for the bottom tier it's actually free (up to 100 builds per month) so it ended up being cheaper than Drone.io.

Original Answer

Drone.io

I just setup our main Ruby on Rails application with http://drone.io/. Was a piece of cake and it's got a great interface. I'd say worth checking out if you're looking for a simple, hosted solution.

Answer 3

Semaphore is a new hosted CI app for Ruby and Rails apps. It integrates with GitHub, requires no setup and has a simple UI.

Answer 4

Integrity seems to be a great solution. Deploying onto heroku is a breeze: http://elabs.se/blog/7-continuous-integration-testing-for-ruby-on-rails-with-integrity http://integrityapp.com

Answer 5

Do it yourself. Write a bash script to run tests and then run a deployment procedure if tests pass. Need notifications? Shoot yourself a plaintext email on success/failure. Need scheduler? Cronjob. This is $0/mo., and you will have a clue as to what you are doing. I do not see how paying someone $40/mo will help me do this in any way more efficient.

Consider for example: my deployment is failing because of an incorrectly configured asset pipeline (assets fail to precompile). This is not going to be caught with unit, functional, integration, regression, or any other tests. This error will not be caught by CI. The amount of time I would spend writing a bash script is likely to be less than the amount of time I would spend setting up a CI environment, and I'll save myself $40/mo.

Juuuuuust throwing my two pennies into the discussion ; )

Answer 6

I just went through the options here and thought I'd roll them up as of late 2011.

Integrity

After a near-death experience that left the still-linked-to website with outdated information and downed the demo site, this project has a spark of life again. But the documentation hasn't moved on, and lots and lots of the steps in the tutorial are just plain broken; I had to change references to gems, build some things out of band, and then I still couldn't get it working.

Cruise Control.rb

Dead simple: you just download it, run a command line to add your project (there is no UI for doing so), and run the Rails app. But there's no UI for editing your project, either, and there's no real integration with build artifacts aside from displaying links to them: you get no graphs of tests run, no trend lines, etc. I also had to adjust the routes.rb file to get the code linking working (the resources :projects line needs to move below all the other non-default routes).

TeamCity

This looks awesome, but the pay scale seems out of whack. 3 agents free and then when you're dependent you need to dole out hundreds of dollars. Personal Builds looks great, but don't have the budget.

Jenkins (née Hudson)

This is a Java stalwart and it is loaded up with a thousand options, so the UI is confusing and it's a chore to set up your projects. But once you set it up you get a whole lot of plugins that can pull from most anywhere, run most anything, and report most everything. The OS X Installer points Jenkins at /Users/Shared/Jenkins/Home but fails to create that directory or chown it to daemon (which is uses by default, and you should change to a new jenkins user so you can set up GitHub integration).

Others

I didn't really try these, but thought I'd mention why:

• CI Joe wants to own the GitHub repo more than I want it, and its creators aren't even using it; they're on Jenkins.
• Cerberus seems neatly small but doesn't have a UI and doesn't automatically publish build artifacts where others can see them.
• BigTuna seems to be a CruiseControl.rb clone without the (already minimal) community support.
• Bamboo looks really neat if you use JIRA and BitBucket, but we use neither. It does deploys but we already have those set up in Capistrano.

The Choice

We went with Jenkins, but I really wish one of the lighter-weight solutions had worked out.