Recently, I wrote about the lack of a mature and de facto standard CI tool in the Ruby community. While not everyone will consider CruiseControl on their Ruby development efforts, for those that do, you now have an option. Late last week, CruiseControl 2.6 was released. In addition to some of the other useful features, RakeBuilder was included. It's now easy to invoke Rake build scripts from CruiseControl.

In late December, I created JIRA issue CC-564, and uploaded the initial version of RakeBuilder, along with supporting classes and configuration changes. The rake tag currently supports three arguments defined in the CruiseControl configuration file. The rakefile to invoke, the target, and the working directory. It's a start, and it worked great on my machine .:-) Like this:

< rake
buildFile="rakefile.rb"
target="default"
workingdir="someworkingdirectory" />

Next, consider downloading Test::Unit::Reporter and output your test results in html or xml format. Then, include other useful utilities like rcov in your rake script, and you've got the foundation of a very nice Continuous Integration solution on your Ruby development efforts.