[Rock-dev] [CruiseControl] rock_bootstrap build cc314b4.24 failed

[Jakob Schwendner]

On 01/27/2011 10:33 AM, Sylvain Joyeux wrote:
> On 01/27/2011 09:29 AM, Jakob Schwendner wrote:
>> On 01/26/2011 02:41 PM, Sylvain Joyeux wrote:
>>> On 01/26/2011 11:07 AM, Peter Soetens wrote:
>>>> I'd prefer that cruisecontrol mails the one that broke the build. 
>>>> I'm this->
>>>> close to filtering out all CruiseControl messages.
>>> OK, but how do you recognize that the current error has the same origin
>>> than the error from yesterday ? Does Hudson do something like that ?
>>> What's your workflow with Hudson at Orocos ?
>> since we are using autoproj for the building and checking out (right?)
>> wouldn't the right process be something like this:
>>
>> * have a text file, which lists the potential suspects (let's call it
>> suspects.txt)
>> * a call to autoproj (I guess it's full-build) will *add* to
>> suspects.txt anyone that appears in the update
>> * a failed build will email anyone in suspects.txt
>> * a successfull build sends a build fixed message to suspects.txt and
>> will *clear* it.
>>
>> thoughts?
>
> In principle, doable. In practice, sounds like quite a bit of work, 
> and relies on the email field on each manifest.xml to be properly 
> filled (which is often not the case).
I would not use the manifest field, but the email in the commit. 
Basically perform an autoproj status before the build-all, and grep all 
email addresses into a file.

Jakob