[ANN] DamageControl - Continuous Integration Server in Ruby

[aslak hellesoy]

Hi Rubyists,

I am one of the developers of DamageControl (DC), a Continuous
Integration server written in Ruby.
I just set it up to build the ruby code itself. As an example - here
are the latest build results: (displays best in firefox or opera - IE
support is not good yet)

http://builds.codehaus.org/damagecontrol/public/project/ruby?dc_creation_time=20041202063806

(see how DC integrates with ViewCVS by following the changeset link of
version.h)

(users with a login would be able to see lots more configuration
options at this url:
http://builds.codehaus.org/damagecontrol/private/project/ruby)

Here is the home page:

http://damagecontrol.codehaus.org/

In case you are unfamiliar with Continuous Integration Servers - it is
a program that detects when developers check in files, then builds the
software and finally communicates the results of the build to
developers via email, irc or other channels. It lets teams deal with
problems in the code early.

DC is a medium size app and a good proof that Ruby can be used for real apps!

I hope someone would find this tool interesting, and would love some
feedback (and even involvement?) from the Ruby community.

Keep in mind that DC is still not officially released - it is not
stable enough for that yet. -But stable enough to be used by brave
people

Cheers,
Aslak

 

[Anders Bengtsson]

Hi Rubyists,

Hi Aslak!

I am one of the developers of DamageControl (DC), a Continuous
Integration server written in Ruby.

Not much response here, but I think it may be because the website more
often than not gives a "Proxy Error", "Error reading from remote
server". (I get the same error from both my home and work computer, so
It's not a problem at this end).

Anyway... DC is really cool, I hope it sees some use from the ruby
developers. Did you try to get it to run some of Ruby's test suites? It
seemed that it only tried to compile when I last looked at it.
Also, the link descriptions in the build list on the left always say
that there were no changes in the build. But when you click on the link
there usually *was* changes for that build. Bug?

/Anders

 

[Florian Weber]

hi!

we are using dc for two projects right now. it helps us greatly!

the only two issues which i would like to see fixed are/were:

- lack of documentation. it got a bit better now, but when i set
it up, the documentation was VERY confusing. it contained
two versions, how it is right now and how it is planned to be
later.

i have to admit though that the documentation is a lot better
now though!

- it would be really nice if dc would include the user
authentication. for sure you can do it via a apache proxy.
but its so nice to just simply use webrick and don't have
to mess with anything else.

other than that dc rules =)

ciao!
florian

 

[gabriele renzi]

aslak hellesoy ha scritto:

Hi Rubyists,

I am one of the developers of DamageControl (DC), a Continuous
Integration server written in Ruby.
I just set it up to build the ruby code itself. As an example - here
are the latest build results: (displays best in firefox or opera - IE
support is not good yet)

http://builds.codehaus.org/damagecontrol/public/project/ruby?dc_creation_time=20041202063806

(see how DC integrates with ViewCVS by following the changeset link of
version.h)

just a thing: this seem to run a 'make test' after the compilation.
Maybe it could do a make test-all to run the test suite too?
Can DC handle stuff like stalling tests ?

Anyway DC seems a great piece of software, congrats.



PS
atm I get 3 errors with ruby's test-all on win32/gcc 3.4.2 (mingw special)

1) Failure:
test_kernel_open(PathnameTest)
[c:/ruby/lib/ruby/1.9/pathname.rb:1197:in `test_kernel_open'
c:/ruby/lib/ruby/1.9/pathname.rb:1195:in `open'
c:/ruby/lib/ruby/1.9/pathname.rb:1195:in `test_kernel_open']:
<2> expected but was
<0>.

2) Failure:
test_eq(TC_Set) [c:/ruby/lib/ruby/1.9/set.rb:1056]:
<#<Set: {"a", "b", #<: {"a", "b", #<: {"a", "b"}>}>}>> expected but was
<#<Set: {#<: {"a", "b", #<: {"a", "b"}>}>, "a", "b"}>>.

3) Error:
test_client_server(Test_Webrick):
TypeError: wrong argument type nil (expected Fixnum)
./test/xmlrpc/webrick_testing.rb:31:in `kill'
./test/xmlrpc/webrick_testing.rb:31:in `stop_server'
./test/xmlrpc/test_webrick_server.rb:54:in `test_client_server'
./test/xmlrpc/test_webrick_server.rb:49:in `each'
./test/xmlrpc/test_webrick_server.rb:49:in `test_client_server'

 

[Michael DeHaan]

We are also damage control users where we work, at least thanks to me.

Great stuff and keep up the good work!

If I had any feature requests it would be sub-projects and a finer
level of build granularity, as we build for about 8+ releases with
about 15+ components each, and right now we only have release-level
granularity, so you have to dig through the logs.

But anyhow, DC is quite awesome. I was able to subclass SCM and
provide for build scheduling by time, all through the UI. Very cool.

--Michael DeHaan

aslak hellesoy ha scritto:

Hi Rubyists,

I am one of the developers of DamageControl (DC), a Continuous
Integration server written in Ruby.
I just set it up to build the ruby code itself. As an example - here
are the latest build results: (displays best in firefox or opera - IE
support is not good yet)

http://builds.codehaus.org/damagecontrol/public/project/ruby?dc_creation_time=20041202063806

(see how DC integrates with ViewCVS by following the changeset link of
version.h)

just a thing: this seem to run a 'make test' after the compilation.
Maybe it could do a make test-all to run the test suite too?
Can DC handle stuff like stalling tests ?

Anyway DC seems a great piece of software, congrats.

PS
atm I get 3 errors with ruby's test-all on win32/gcc 3.4.2 (mingw special)

1) Failure:
test_kernel_open(PathnameTest)
[c:/ruby/lib/ruby/1.9/pathname.rb:1197:in `test_kernel_open'
c:/ruby/lib/ruby/1.9/pathname.rb:1195:in `open'
c:/ruby/lib/ruby/1.9/pathname.rb:1195:in `test_kernel_open']:
<2> expected but was
<0>.

2) Failure:
test_eq(TC_Set) [c:/ruby/lib/ruby/1.9/set.rb:1056]:
<#<Set: {"a", "b", #<: {"a", "b", #<: {"a", "b"}>}>}>> expected but was
<#<Set: {#<: {"a", "b", #<: {"a", "b"}>}>, "a", "b"}>>.

3) Error:
test_client_server(Test_Webrick):
TypeError: wrong argument type nil (expected Fixnum)
./test/xmlrpc/webrick_testing.rb:31:in `kill'
./test/xmlrpc/webrick_testing.rb:31:in `stop_server'
./test/xmlrpc/test_webrick_server.rb:54:in `test_client_server'
./test/xmlrpc/test_webrick_server.rb:49:in `each'
./test/xmlrpc/test_webrick_server.rb:49:in `test_client_server'