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: How we treat broken builds.
Date Wed, 20 Feb 2013 22:15:59 GMT
On Wed, Feb 20, 2013 at 09:53:43AM -0500, David Nalley wrote:
> 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
>

Yes, I'll email builds@ now.


Mime
View raw message