incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chip Childers <chip.child...@sungard.com>
Subject Re: test lifecycle
Date Thu, 13 Sep 2012 18:58:59 GMT
Noah,

We had discussed this, and opted to send them to
cloudstack-commits@incubator.apache.org for general purpose review,
with the "Send separate e-mails to individuals who broke the build"
option checked.

-chip

On Thu, Sep 13, 2012 at 2:55 PM, Noah Slater <nslater@tumbolia.org> wrote:
> Are there any plans to send build failures to the dev mailing list? Might
> be useful, might not be. :)
>
> On Wed, Sep 12, 2012 at 9:16 PM, David Nalley <david@gnsa.us> wrote:
>
>> Hi folks,
>>
>> I am thinking about making some changes to jenkins and figured I'd
>> toss it up here before I do it to make sure no one disagrees.
>>
>> Here's my frustration: We are getting spammed by lots of jenkins
>> notices, many needlessly.
>>
>> Prime example: junit failures when the build also failed. IMO we
>> shouldn't even try running the unit tests as there is an explicit
>> dependency to compile and we 'know' it won't build.
>>
>> So I'd run build-$branch on each commit - if successful it would
>> trigger build-marvin, build-docs, build-apidocs, and junit. If junit
>> succeeds build packages (though eventually we probably want to
>> run-marvin first, but for the moment)
>>
>> Thoughts, comments, flames?
>>
>> --David
>>
>
>
>
> --
> NS

Mime
View raw message