From: Jeff <cohen.jeff@...>
Date: 2007-03-15T04:15:02+09:00
Subject: Re: CruiseControl.rb 1.0


On Mar 12, 11:27 pm, "Alexey Verkhovsky" <alexey.verkhov...@gmail.com>
wrote:
> Hmmm.  Another Continuous Integration tool?  What is that, the millionth
> one?

I have a feeling this is going to sound like a stupid question, but
why does anyone need a continuous integration tool for a dynamic
language like Ruby?  In other words, what exactly in my subversion
repository is it going to "build"?

When I used to work with .NET, it was helpful to have daily binaries
from source, so that we could run the test suite, or be able to
install the latest build on a test machine somewhere.

But with Rails, for example, I run my tests *before* I commit to
subversion - it was pretty easy to write a rake task to run the tests,
and then commit the code automatically if all of the tests passed.
The same could be said for any Ruby project, not just Rails.

Maybe I'm thinking in a narrow way, based on my limited experience
with Ruby and Rails projects so far.  So I'm just curious, and to
expand my own horizons a bit - what are some examples of when a Ruby
developer would need a continuous integration tool?

Thanks!
Jeff