qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famcool@gmail.com>
Cc: John Snow <jsnow@redhat.com>, Fam Zheng <famz@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Patch checking bot
Date: Wed, 22 Oct 2014 11:08:06 +0100	[thread overview]
Message-ID: <20141022100806.GD8798@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CABgc4wSWqZa2e=A7yd13MJP+nxpXh-tt=dOt5xjWHqbjvSd26w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

On Tue, Oct 21, 2014 at 04:19:52PM +0800, Fam Zheng wrote:
> On Mon, Oct 20, 2014 at 6:25 PM, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > Use docker or lxc to run a container for builds.  The root file system
> > should be fresh for each build so previous builds cannot affect later
> > ones.  The container cannot have external networking connectivity (for
> > security).
> 
> A small question: if the container doesn't have network connectivity,
> where does the bot's checking scripts read the patch mail from?

The bot runs outside the container.  It uses 'patches fetch' to grab the
latest patches database every 15 minutes or so.

When a new patch series is detected, it creates a new container and
places an mbox that git-apply(1) can process inside the container.

The rest happens inside the container:

  cd qemu
  scripts/checkpatch.pl </tmp/patches.mbox
  git apply </tmp/patches.mbox
  ./configure ... && make
  make check check-block

Once the checker completes the bot can update the status web page and
send out an error report email, if necessary.

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2014-10-22 10:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 10:25 [Qemu-devel] Patch checking bot Stefan Hajnoczi
2014-10-20 14:08 ` Peter Maydell
2014-10-21 15:27   ` John Snow
2014-10-22 10:03   ` Stefan Hajnoczi
2014-10-27 18:25     ` Andreas Färber
2014-10-21  8:19 ` Fam Zheng
2014-10-22 10:08   ` Stefan Hajnoczi [this message]

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=20141022100806.GD8798@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=famcool@gmail.com \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=qemu-devel@nongnu.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).