From: Daniel Gollub <gollub@b1-systems.de>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Avi Kivity <avi@redhat.com>, Gleb Natapov <gleb@redhat.com>,
kvm@vger.kernel.org, Christian Berendt <berendt@b1-systems.de>
Subject: Re: buildbot
Date: Wed, 8 Jul 2009 17:51:39 +0200 [thread overview]
Message-ID: <200907081751.43909.gollub@b1-systems.de> (raw)
In-Reply-To: <4A54B8D1.5050703@web.de>
[-- Attachment #1: Type: text/plain, Size: 3235 bytes --]
On Wednesday 08 July 2009 05:18:41 pm Jan Kiszka wrote:
> > Some further questions to the build test:
> >
> > - incremental/quick or full/"safe" build tests?
> > (e.g. "make clean" before actual configuration/build?)
>
> Maybe a full rebuild once per day and incremental rebuilds for each
> update.
Buildbot has a scheduler called "Nightly", which would perfectly fit here. You
can schedule those full builds on e.g.: 23:00
> I bet there will be a way to trigger also full rebuilds manually
> in case something looks fishy, right?
Not quite sure - need to check that. But there is buttoon "force build" on the
web interface to retrigger a build, even if there was no "event" (e.g.
commit). But this would also call the Build-Profile without the "make clean".
But we could create a "cleanup" Build-Profile, which is using the same build
directory. And do this "force build" for this "cleanup" Build-Profile.
But very likely there is such a feature and i just didn't found it yet ....
>
> > - any non-default compiler flags?
>
> Use as many as you can. Make sure all required libs are available on the
> host so that qemu(-kvm) enables the related features (e.g. xen).
Ok.
>
> > - which combination of configuration should get tested?
> > * w/o --disable-kvm
> > * ...
> > - which branches should get build-tested for qemu-kvm.git? just master in
> > the beginning?
>
> Further wishes (I didn't thought too much about it, be prepared for more
>
> :->):
>
> - out-of-tree build (currently broken in qemu-kvm)
With every commit, or nightly/once-per-day?
> - building for 32 and 64-bit hosts
Yes, thats planned.
>
> Thanks for your effort so far! But I hope you are aware of the fact that
> maintaining the buildbot will also require some work.
Sure, i already discussed that with my manager. I guess some of my colleagues
will also support me on maintaing this environment ...
> I would suggest to
> either make the setup description and scripts available for cloning your
> environment easily or arrange access for further contributors to
> distribute maintenance as far as reasonable and feasible.
It's planned to setup the buildmaster in a VM. So if there is any HW failure
or I run out of time, i would just handover the VM to someone else. The VM is
dedicated to the buildmaster ...
I thought also about running a Git repository for the used buildmaster
configuration. Since the master configuration contains all the build profiles.
> I would be
> someone interested in helping (as I hope it will safe me quite some time
> elsewhere).
Ok - cool. As soon the VM is up and running i'll contact you regarding remote
access.
Best Regards,
Daniel
--
Daniel Gollub Geschaeftsfuehrer: Ralph Dehner
FOSS Developer Unternehmenssitz: Vohburg
B1 Systems GmbH Amtsgericht: Ingolstadt
Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537
EMail: gollub@b1-systems.de http://www.b1-systems.de
Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg
http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-07-08 15:51 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 ` buildbot Avi Kivity
2009-07-08 15:18 ` buildbot Jan Kiszka
2009-07-08 15:51 ` Daniel Gollub [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=200907081751.43909.gollub@b1-systems.de \
--to=gollub@b1-systems.de \
--cc=avi@redhat.com \
--cc=berendt@b1-systems.de \
--cc=gleb@redhat.com \
--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.