Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <20130219163251.GG7961@USLT-205755.sungardas.corp>
References: 
 <CAKprHVbfOqwcOX0AiVgYwcDzQp3iTr9RQ_bhb-WdD1Lg-HZWQg@mail.gmail.com>
 <CALFpzo517Dwst=54WOeuVa1gEVYJ=yT7V39r-QXN1OYODLGy9w@mail.gmail.com>
 <CALFpzo7xid1mQdnCSiuVw9yj6AoADORWKZ1yEwypc9zS=jJD1A@mail.gmail.com>
 <CAKprHVb2JzbebysdjoMSm6B-VeLNKA+5zy3bgnt1ay9v10tVLw@mail.gmail.com>
 <20130219163251.GG7961@USLT-205755.sungardas.corp>
From: David Nalley <david@gnsa.us>
Date: Wed, 20 Feb 2013 09:53:43 -0500
Message-ID: 
 <CAKprHVZ5neqwFVZ4NRB4CLvmUgP=VtvtjG5wRCAnh25MVM1wew@mail.gmail.com>
Subject: Re: How we treat broken builds.
To: cloudstack-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Feb 19, 2013 at 11:32 AM, Chip Childers
<chip.childers@sungard.com> wrote:
> On Sun, Feb 17, 2013 at 10:31:44PM -0500, David Nalley wrote:
>> On Sun, Feb 17, 2013 at 9:03 PM, Marcus Sorensen <shadowsor@gmail.com> wrote:
>> > Are there jenkins reports the committers can subscribe to and get email
>> > when there are breakages? I know at least once 4.1 was broken while I was
>> > in the process of testing a commit (just a quick sanity check I do to avoid
>> > being the guy who causes these sorts of things), and then I committed on
>> > top of that broken branch. If there are such emails (and I suspect there
>> > are), it would help me to know when to stop working on the branch, and all
>> > of the committers should probably sign up.
>> > On Feb 17, 2013 6:44 PM, "David Nalley" <david@gnsa.us> wrote:
>> >
>>
>>
>> Yes there are - the commits mailing list receives the notifications
>> from both jenkins.cs.o and builds.a.o.
>> Thanks for asking the question, I just assumed everyone knew of, and
>> was subscribed to the mailing list.
>>
>> You can subscribe by sending an email to:
>>
>> cloudstack-commits-subscribe@incubator.apache.org
>>
>> --David
>>
>
> I've noticed that although builds.a.o is configured to email the
> committers when the build breaks for their changes, it's sending to
> weird addresses.  For example, I see it sending notices to
> chip.childers@apache.org, which doesn't exist.  It seems to take the
> username from the committer email address, and then use @a.o.  Weird.
>
> Also, perhaps we can configure the jobs to email build failures and "all
> better" emails to the dev list instead of commits?  I know that
> committers should be watching the commits, but I bet that doesn't happen
> in real time...  and that the dev list would be a better place to get
> attention a little more quickly.
>


That is weird. Probably an artifact of how userids are treated in SVN.
Something to bring up with builds@.
I am okay with that change - I assume you are going to make it?

--David