From: Avi Kivity <avi@redhat.com>
To: Daniel Gollub <gollub@b1-systems.de>
Cc: Jan Kiszka <jan.kiszka@web.de>, Gleb Natapov <gleb@redhat.com>,
kvm@vger.kernel.org, Christian Berendt <berendt@b1-systems.de>
Subject: Re: buildbot
Date: Wed, 08 Jul 2009 18:07:57 +0300 [thread overview]
Message-ID: <4A54B64D.104@redhat.com> (raw)
In-Reply-To: <200907081645.08954.gollub@b1-systems.de>
On 07/08/2009 05:45 PM, Daniel Gollub wrote:
> A local instance of buildbot with one master and one slave is already running
> for qemu-kvm.git (clone). Preparing now the final buildmaster host ...
>
> Unfortunately there seems to be no Git-"poller" in buildbot, like for SVN. So
> there is need to install a Git post-receive hook on the repositories to
> trigger the buildbot-master:
> http://buildbot.net/trac/browser/contrib/git_buildbot.py
>
> I hope this ok. Otherwise we would need to setup mirror, which contains this
> hook.
>
I can easily add the hook.
> Some further questions to the build test:
>
> - incremental/quick or full/"safe" build tests?
> (e.g. "make clean" before actual configuration/build?)
>
I think clean builds + ccache give a good safety/performance tradeoff.
qemu is pretty safe wrt incremental builds anyway.
> - any non-default compiler flags?
>
Not from me, but if someone has a favorite flag, we can test it.
> - which combination of configuration should get tested?
> * w/o --disable-kvm
> * ...
>
Let's hear the list...
> - which branches should get build-tested for qemu-kvm.git? just master in the
> beginning?
>
master, next, stable-0.10
I also want more repositories: qemu.git, kvm.git, and kvm-kmod.git. The
latter will be tricky since it references another repository, but we'll
work it out.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-07-08 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 14:35 [PATCH][RESEND] Add kvm_set_boot_cpu_id() API Gleb Natapov
2009-07-07 9:56 ` Avi Kivity
2009-07-07 18:45 ` Jan Kiszka
2009-07-07 19:47 ` buildbot Avi Kivity
2009-07-07 20:53 ` buildbot Daniel Gollub
2009-07-08 4:54 ` buildbot Avi Kivity
2009-07-08 14:45 ` buildbot Daniel Gollub
2009-07-08 15:07 ` Avi Kivity [this message]
2009-07-08 15:18 ` buildbot Jan Kiszka
2009-07-08 15:51 ` buildbot Daniel Gollub
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=4A54B64D.104@redhat.com \
--to=avi@redhat.com \
--cc=berendt@b1-systems.de \
--cc=gleb@redhat.com \
--cc=gollub@b1-systems.de \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.