Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of nslater@tumbolia.org designates
 209.85.220.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKprHVZwG2NsNuObP0tCxosgn2MxomkyXYVQ7m4oGGFeJz7_xA@mail.gmail.com>
References: 
 <CAKprHVZwG2NsNuObP0tCxosgn2MxomkyXYVQ7m4oGGFeJz7_xA@mail.gmail.com>
Date: Thu, 13 Sep 2012 19:55:00 +0100
Message-ID: 
 <CA+Y+444UfABGdaM_gqkYEpkC7HGoghs54Bv3+zgprT2dsm3i1A@mail.gmail.com>
Subject: Re: test lifecycle
From: Noah Slater <nslater@tumbolia.org>
To: cloudstack-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b4140c625525e04c999d8e2

--047d7b4140c625525e04c999d8e2
Content-Type: text/plain; charset=ISO-8859-1

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

--047d7b4140c625525e04c999d8e2--