public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Andreas Färber" <afaerber@suse.de>,
	"KVM devel mailing list" <kvm@vger.kernel.org>,
	"Juan Quintela" <quintela@redhat.com>,
	"qemu-devel qemu-devel" <qemu-devel@nongnu.org>,
	"Anthony Liguori" <anthony@codemonkey.ws>,
	"Christian Berendt" <berendt@b1-systems.de>,
	"Daniel Gollub" <gollub@b1-systems.de>
Subject: Re: [Qemu-devel] QEMU buildbot maintenance state
Date: Wed, 30 Jan 2013 10:31:22 +0100	[thread overview]
Message-ID: <5108E86A.5040207@redhat.com> (raw)
In-Reply-To: <20130129123336.GA10681@stefanha-thinkpad.redhat.com>

  Hi,

> Gerd: Are you willing to co-maintain the QEMU buildmaster with Daniel
> and Christian?  It would be awesome if you could do this given your
> experience running and customizing buildbot.

I'll try to set aside some time for that.  Christians idea to host the
config at github is good, that certainly makes it easier to balance
things to more people.

Another thing which would be helpful:  Any chance we can setup a
maintainer tree mirror @ git.qemu.org?  A single repository where each
maintainer tree shows up as a branch?

This would make the buildbot setup *alot* easier.  We can go for a
AnyBranchScheduler then with BuildFactory and BuildConfig shared,
instead of needing one BuildFactory and BuildConfig per branch.  Also
makes the buildbot web interface less cluttered as we don't have a
insane amount of BuildConfigs any more.  And saves some resources
(bandwidth + diskspace) for the buildslaves.

I think people who want to look what is coming or who want to test stuff
cooking it would be a nice service too if they have a one-stop shop
where they can get everything.

cheers,
  Gerd

  reply	other threads:[~2013-01-30  9:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 10:59 KVM call agenda for 2013-01-29 Juan Quintela
2013-01-28 13:02 ` [Qemu-devel] " Andreas Färber
2013-01-28 14:29   ` QEMU buildbot maintenance state (was: Re: KVM call agenda for 2013-01-29) Daniel Gollub
2013-01-28 15:10     ` QEMU buildbot maintenance state Andreas Färber
2013-01-29 12:33     ` [Qemu-devel] QEMU buildbot maintenance state (was: Re: KVM call agenda for 2013-01-29) Stefan Hajnoczi
2013-01-30  9:31       ` Gerd Hoffmann [this message]
2013-01-30 14:41         ` [Qemu-devel] QEMU buildbot maintenance state Anthony Liguori
2013-01-31 12:54         ` Stefan Hajnoczi
2013-01-31 12:58           ` Christian Berendt
2013-02-01 17:22             ` Christian Berendt
2013-01-31 12:55         ` Stefan Hajnoczi
2013-01-29 15:04     ` Christian Berendt
2013-01-30  9:39       ` Stefan Hajnoczi
2013-01-28 13:29 ` KVM call agenda for 2013-01-29 Stefan Hajnoczi
2013-01-28 14:14 ` Anthony Liguori
2013-01-29  8:49   ` Alexander Graf
2013-01-29 10:01     ` Peter Maydell
2013-01-29 13:02 ` Andreas Färber

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=5108E86A.5040207@redhat.com \
    --to=kraxel@redhat.com \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=berendt@b1-systems.de \
    --cc=gollub@b1-systems.de \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=stefanha@gmail.com \
    /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