From: Tanner Burson Date: 2007-03-15T05:01:12+09:00 Subject: Re: CruiseControl.rb 1.0 ------=_Part_52303_33356840.1173902425898 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 3/14/07, Jeff wrote: > > > On Mar 12, 11:27 pm, "Alexey Verkhovsky" > 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. I actually plan on using this FOR .NET development. While CC.Net is useful, it isn't going to help me with my linux based Mono builds. This could be an extremely useful tool for those of us building cross platform software, and wanting a simple CI tool to use for multiple languages. 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 > > > -- ===Tanner Burson=== tanner.burson@gmail.com http://www.tannerburson.com ------=_Part_52303_33356840.1173902425898--