From estebanm at opera.com  Fri Oct 19 11:06:28 2007
From: estebanm at opera.com (=?utf-8?Q?Esteban_Manchado_Vel=C3=A1zquez?=)
Date: Fri, 19 Oct 2007 17:06:28 +0200
Subject: [Cruisecontrolrb-developers] Possible patch, and question
Message-ID: <op.t0f9k2woqcqbbv@estebanm-desktop>

Hi,

    I'm using CruiseControl.rb, and I wrote a dirty patch to add basic  
support for some result "statistics" (fixes, regressions and test failures  
in a build).

    I was going to clean it up and send, and then I saw the functionality  
that is there already for reporting test failures (as a list, not  
"statistics", but most of the code could be used for the same). I mean  
get_test_failures_and_errors_if_any and friends.

    Are you interested in such a patch? My idea is making the test failure  
reporting functionality generic, so you can define your own classes, with  
their own regular expressions and such, to support other kinds of projects  
(not just Ruby). I'll also add those "statistics" about fixes and  
regressions for each build, but I can prepare a separate patch for that.

    Also, a question related to the patch: for the projects to be able to  
configure the test result "parser", I need to access the project  
configuration (duh!), but it seems it's not possible because Project.read  
is called with load_config = false in app/models/projects.rb (load_project  
method). When I changed to "true", everything worked as (I) expected. Is  
loading the project configuration on startup a problem? Is there some  
other, better way to read the configuration for the projects?

-- 
Esteban Manchado Vel?zquez <estebanm at opera.com>, who kind of hates current  
internal Opera builds

From estebanm at opera.com  Tue Oct 30 13:51:02 2007
From: estebanm at opera.com (=?utf-8?B?RXN0ZWJhbiBNYW5jaGFkbyBWZWzDg8aSw4LCoXpxdWV6?=)
Date: Tue, 30 Oct 2007 18:51:02 +0100
Subject: [Cruisecontrolrb-developers] Contributors agreement?
Message-ID: <op.t00ujcuh8dt880@estebanm-desktop>

Hi,

    I have rewritten my patch, and I think it's almost done. I have to  
delete some old cruft and write some unit tests for it, but that shouldn't  
take much time.

    So, I was preparing myself to make the patch public, but I thought that  
I would have to ask for permission first (I mean my company). So I went to  
the CC.rb website, to look for the agreement... but the agreement link  
returns a 404 :-((

    http://cruisecontrolrb.thoughtworks.com/documentation/contributors_agreement.html

Anyone?

-- 
Esteban Manchado Vel?zquez <estebanm at opera.com>, who doesn't hate current  
internal Opera builds anymore