definitely agree that the state of CI projects for Ruby/Rails is not great. I was using CruiseControl.rb on Rails 2.x with success, but getting it to play well when moving to Bundler/RVM was way more difficult than it should have been.
I always thought Integrity showed promise, but then you have this: http://builder.integrityapp.com/integrity
It's Integrity watching itself, and the last build from Jun 26th has failed. That doesn't inspire confidence.
So for now, I'm sticking with Hudson. It is a bit heavier, but it's available as a package on Ubuntu, so installing and maintaining is cake. I also like that fact that its flexible to do builds for any platform/codebase, which lets me consolidate all CI into one CI app.
I have mine configured to pop a little window on Ubuntu any time a change causes a test to fail. It is quite motivational and has saved my bacon many, many times these last few weeks.
It isn't really great for using for e.g. running a suite of expensive Selenium tests frequently, but it cranks out simple unit, functional, and API tests.
Autotest is not CI. A key component of a good CI setup is having a "pure" system that builds your application code. The purpose of this is to ensure that a machine, other than your own, can actually build your software. This is to reveal hidden dependencies, or sometimes differences between your dev box and the production environment.
12 comments
[ 2.6 ms ] story [ 30.4 ms ] threadI always thought Integrity showed promise, but then you have this: http://builder.integrityapp.com/integrity It's Integrity watching itself, and the last build from Jun 26th has failed. That doesn't inspire confidence.
So for now, I'm sticking with Hudson. It is a bit heavier, but it's available as a package on Ubuntu, so installing and maintaining is cake. I also like that fact that its flexible to do builds for any platform/codebase, which lets me consolidate all CI into one CI app.
For solo Rails developers who want the automation but don't want to deal with big icky configuration, can I recommend autotest?
http://ph7spot.com/musings/getting-started-with-autotest
I have mine configured to pop a little window on Ubuntu any time a change causes a test to fail. It is quite motivational and has saved my bacon many, many times these last few weeks.
It isn't really great for using for e.g. running a suite of expensive Selenium tests frequently, but it cranks out simple unit, functional, and API tests.
we just uploaded some screenshots - http://bigtuna.appelier.com/screenshots.html
Demo will come soon.
good job.. looks good! :) will definitely check it out.
http://builder.bigtuna.appelier.com/