Greetings,
I’ve a project going that has multiple team members, supports multiple
processor architectures and multiple languages. We’re writing in Ruby
(with test cases) and we interface to c and c++ using swig.
Configuration management is done with subversion.
Now with everyone working on the project and having all the platforms
that need to be supported, I would like to install a continuous
integration tool. The idea is to trigger the tool from svn commits,
rebuild and run all the test cases in each of the environments.
Cruise Control is clearly the most widely known tool. However, I’m
building with rake and make (from the extconf generated with the swig
stuff) neither of which appear to be supported (by default) by CC. I
read somewhere that someone was working a CC equivalent in Ruby but have
lost that information.
So, what is the tool of choice for this group of folks to driver a
continuous integration activities?
Thanks,
-dwh-
–
I not only live each endless day in grief, but live each day
thinking about living each day in grief.
– C.S. Lewis
Daniel W. Hinz Xerox Corp: XOG/SEBU/MCD/EIDC/ISM&D
MS: 111-03J e-mail: [email protected]
800 Phillips Road TEL: 585.422.8078
Webster, NY 14580
Dan H. wrote:
rebuild and run all the test cases in each of the environments.
Cruise Control is clearly the most widely known tool. However, I’m
building with rake and make (from the extconf generated with the swig
stuff) neither of which appear to be supported (by default) by CC. I
read somewhere that someone was working a CC equivalent in Ruby but have
lost that information.
So, what is the tool of choice for this group of folks to driver a
continuous integration activities?
You come a little too early 
I recently started coding such a beast and I have it at a stage where it
builds, tests and also updates/configures the project servers for my
current project.
It’s a small framework (four base classes and a couple of useful
implementations) but by no means ready for public consumption.
Currently I drive a rake/dmake/msbuild build with rdoc and doxygen
generation so I guess I have enough variety :).
The system is dRuby-based at the moment but the concept can be
implemented with Rails or whatever else you like.
I looked around for something that would handle the variety of build
methods my project has and DamageControl looked the more promising, but
I haven’t seen any movement on that project since before RubyConf and
the other alternatives (CC etc. ) were just too specialized.
I guess with a bit of coding SwitchTower can be made into a continuous
integration tool as well (is actually very easy)
Cheers,
V.-
–
http://www.braveworld.net/riva
FWIW, I recently used CruiseControl for a C++/make project. I simply
wrapped the make build in a basic ant script, using ant’s ability to
call external shell processes (this was on linux…). The same
approach should work with tools like Rake.
dean
On 1/4/06, Damphyr [email protected] wrote:
So, what is the tool of choice for this group of folks to driver a
continuous integration activities?
…
–
Dean W.
http://www.aspectprogramming.com
http://www.newaspects.com
http://www.contract4j.org
Damage Control is what you want.
Unfortunately, I just googled to find a URL to give you and there
doesn’t appear to be any good information available.
I’m copying Aslak and hopefully we’ll have public information
available soon. I know that he’s been working very hard on it for
several months now and I’m pretty sure there is a release forthcoming.