The quest for a decent Ruby Continuous Integration tool

Git has become very popular in the Ruby community. Github in particular has become a focal point for Ruby innovation. So which Continuous Integration tools support Git and Rake (the Ruby community’s build tool of choice)? I’ve been trying a few out for the 1Click2Fame build process.

What I am looking for is a Continuous Integration server that:

  • supports Rake
  • supports Git, via Github
  • can run multiple agents (I want to test our website against many operating systems)
  • can stop a running build (sometimes, you know it’s not going to work out)
  • has a configuration gui

First out the gate is the daddy of Continuous Integration tools, CruiseControl. It supports both git and rake out of the box. Good.

Pros:

  • It works
  • I know it very well

Cons:

  • It works on a single node
  • You can’t stop a build
  • No GUI (unless you go visit Al Wick)
  • The new Java GUI doesn’t render Ruby output very well. The XSL approach may have been as old as the hills, but people did tinker with it.

Next out is CruiseControl.rb. This project was sponsored by ThoughtWorks as a way to make it easier for Ruby projects to use Continuous Integration. I kind of hate it. The original CruiseControl ended up releasing Rake support before the Ruby port happened.

Anyway, it’s done. There used to be this meme that you had to have a CI server written in the language that your engineers wrote every day. I don’t think that’s the case now. These days, I’d suggest that you could do something cool with JRuby to not write all that code yet again (ThoughtWorks were forced to port CruiseControl to .NET by a customer who actually banned Java code from their site – not at all insecure then).

It supports both git and rake, but it’s always felt a little fiddly to me. You have to add a project from the shell on the machine, not from the GUI. The Git support seems like an aftermarket accessory rather than a factory option. Here’s how it stacks up:

Pros:

  • It works
  • Ruby hackers can hack it
  • It does render rake output nicely, until you reach a limit, and then it truncates the output. You can see the full raw output.

Cons:

  • Single node
  • Can’t stop a build
  • No Config GUI

While CC.rb works, it’s not rocking our world. The quest for Continuous Integration greatness continues. Next episode: Cruise.


5 thoughts on “The quest for a decent Ruby Continuous Integration tool

  1. Al Snow says:

    Check out RunCodeRun

  2. Will Sargent says:

    Honestly, Hudson has worked out so amazingly well, I’m surprised it’s not more popular.

    * supports Rake [check]
    * supports Git, via Github [check, via plugin]
    * can run multiple agents (I want to test our website against many operating systems) [check, via master/slave]
    * can stop a running build (sometimes, you know it’s not going to work out) [check]
    * has a configuration gui [check]

    It also for allows test graphs and breakdowns of tests, through ci_reporter, and can integrate with JIRA automagically.

  3. […] своего проекта написанного на Ruby в CruiseControl и CC.rb http://www.build-doctor.com/2009/04/06/the-quest-for-a-decent-ruby-continuous-integration-tool . Ð’ принципе обоими из них он остался недоволен, при […]

  4. […] I posted, I’m on a quest for the right CI server for 1Click2Fame. I had some helpful suggestions in […]

  5. […] #9 we have The quest for a decent Ruby Continuous Integration tool. In 2009, Ruby support improved for several CI […]

Comments are closed.

%d bloggers like this: