From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Buildbot + registry errors
Date: Mon, 25 Apr 2011 10:04:06 +0200 [thread overview]
Message-ID: <87wrii69l5.fsf@randomsample.de> (raw)
In-Reply-To: <87pqobf002.fsf@lifelogs.com> (Ted Zlatanov's message of "Sun, 24 Apr 2011 23:06:21 -0500")
Ted Zlatanov writes:
> On Sun, 24 Apr 2011 21:29:47 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
>
> LMI> Whenever somebody checks something in, they get a message about the
> LMI> failed build
>
> That seems like something BuildBot should not be doing. It should CC
> everyone involved since the LAST failure, not just the last committer.
Here's the current (since Apr 21st) setup:
- The buildbot checks the git repo about 10x per hour.
- If it finds a new HEAD, it pulls and runs the builders.
- If a build was OK previously but now fails, it will send a mail
- to the buildbot mailinglist
- to every committer who was part in generating the new HEAD (the so
called "blamelist").
- If a build failed again (meaning it also failed in the previous
build), a mail will *only* be sent to the buildbot mailinglist.
> But my problem was that I forgot to subscribe to the buildbot mailing
> list. "It's so quiet around here..."
The buildbot did send a mails directly to you when the build initially
broke:
2011-04-20 23:11:13 1QCeQL-0001Jb-JT => tzz@lifelogs.com ...
2011-04-20 23:11:13 1QCeQL-0001Jb-JT Completed
2011-04-20 23:11:14 1QCeRS-0001ZZ-FM => tzz@lifelogs.com ...
2011-04-20 23:11:14 1QCeRS-0001ZZ-FM Completed
Didn't those came through? The domain has proper DKIM signing, SPF and
all that.
-David
next prev parent reply other threads:[~2011-04-25 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 19:29 Lars Magne Ingebrigtsen
2011-04-24 19:42 ` David Engster
2011-04-25 4:06 ` Ted Zlatanov
2011-04-25 8:04 ` David Engster [this message]
2011-04-25 12:24 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wrii69l5.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).