From: Daniel Gollub <gollub@b1-systems.de>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>,
Christian Berendt <berendt@b1-systems.de>
Subject: Re: buildbot for kvm.git
Date: Thu, 25 Nov 2010 09:48:54 +1300 [thread overview]
Message-ID: <201011250948.56864.gollub@b1-systems.de> (raw)
In-Reply-To: <4CECE7A9.3090509@redhat.com>
[-- Attachment #1: Type: Text/Plain, Size: 1938 bytes --]
On Wednesday, November 24, 2010 11:23:37 pm Avi Kivity wrote:
[...]
> I think buildbot has a mechanism where you can send it a patch to be
> build-tested. This allows developers to build-test on architectures
> they don't have. Can we activate this?
Sure. Just enabled that. Actually it's also available for qemu-kvm.git but
never really got used.
Who should get access to this? I wouldn't make it available for anonymous,
since someone could checkin an "evil"-patch for a makefile, which includes "rm
-rf /this/and/that" and vanish the buildslave.
I'm fine giving (personal) user accounts away for people who just ask for it.
Or do you want to make this only available for a small (trusted) group?
Try-Build would get triggerd with the buildbot command (on developers
workstation) like this:
$ cd kvm.git
... do some changes ...
$ buildbot try --vc git -c pb -m buildbot.b1-systems.de:8033 -b s390 \
-u $USER --passwd=$PASSWORD
[...]
> > > configs:
> > > x86_64: defconfig + KVM=m KVM_INTEL=m KVM_AMD=m
> > > i386: defconfig + KVM=m KVM_INTEL=m KVM_AMD=m
> >
> > Without virtio? intentionally?
>
> No, that's my old configuration I used for build testing. While virtio
> isn't part of kvm, and is arch-neutral, it would be good to enable it.
Ok. I see - was just wondering because it was set in your powerpc
configurations but not for others.
>
> > > The recipe for a build is:
> > > - check out the source
> >
> > Any specific branches beside the master branch?
>
> master and next.
done.
On the next kvm.git push the buildbot should trigger a build test for
branches: master and next.
Best Regards,
Daniel
--
Daniel Gollub
Linux Consultant & Developer
Mail: gollub@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-11-24 20:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 13:31 buildbot for kvm.git Avi Kivity
2010-11-10 13:33 ` Avi Kivity
2010-11-10 15:02 ` Alexander Graf
2010-11-10 15:03 ` Avi Kivity
2010-11-10 15:40 ` Alexander Graf
2010-11-11 9:22 ` Daniel Gollub
2010-11-22 9:37 ` Avi Kivity
2010-11-23 0:11 ` Daniel Gollub
2010-11-23 10:22 ` Avi Kivity
2010-11-24 20:51 ` Daniel Gollub
2010-11-24 10:15 ` Daniel Gollub
2010-11-24 10:23 ` Avi Kivity
2010-11-24 20:48 ` Daniel Gollub [this message]
2010-11-25 9:22 ` Avi Kivity
2010-11-29 11:36 ` Daniel Gollub
2010-11-29 12:20 ` Jan Kiszka
2010-11-29 19:22 ` Daniel Gollub
2010-11-30 9:12 ` Jan Kiszka
2010-11-24 21:03 ` Daniel Gollub
2010-11-25 1:20 ` Alexander Graf
2010-11-25 9:17 ` Avi Kivity
2010-11-30 10:47 ` buildbot for kvm.git is now live (was: Re: buildbot for kvm.git) 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=201011250948.56864.gollub@b1-systems.de \
--to=gollub@b1-systems.de \
--cc=avi@redhat.com \
--cc=berendt@b1-systems.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.