From: Paolo Bonzini <pbonzini@redhat.com> To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>, "Daniel P. Berrangé" <berrange@redhat.com> Cc: "Peter Maydell" <peter.maydell@linaro.org>, "Samuel Ortiz" <sameo@linux.intel.com>, "Kashyap Chamarthy" <kchamart@redhat.com>, "Philippe Mathieu-Daudé" <philmd@redhat.com>, "Richard Henderson" <richard.henderson@linaro.org>, "QEMU Developers" <qemu-devel@nongnu.org>, "Stefan Hajnoczi" <stefanha@redhat.com>, "Alex Bennée" <alex.bennee@linaro.org> Subject: Re: [Qemu-devel] more automated/public CI for QEMU pullreqs Date: Thu, 22 Aug 2019 18:48:08 +0200 Message-ID: <9caf3a64-0841-dde6-3413-a77dc80e22bd@redhat.com> (raw) In-Reply-To: <20190822163150.GA3332@work-vm> On 22/08/19 18:31, Dr. David Alan Gilbert wrote: >> With both these points in mind, I think it is pretty hard sell to >> say we should write & maintain a custom CI system just for QEMU >> unless it is offering major compelling functionality we can't do >> without. In theory I agree. In practice, the major compelling functionality is portability. If it is true that setting up runners is problematic even on aarch64, frankly GitLab CI is dead on arrival. If it is not true, then I'd be very happy to use GitLab CI too. Paolo > I'd agree; and I'd also find it useful to have runners setup for > Gitlab CI for related things (it would be useful for the virtio-fs > stuff); if there are problems on other architectures then we should > find some go wranglers to go fix it.
next prev parent reply index Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-16 18:16 Peter Maydell 2019-08-22 10:49 ` Stefan Hajnoczi 2019-08-22 11:04 ` Peter Maydell 2019-08-22 11:14 ` Paolo Bonzini 2019-09-30 12:53 ` Peter Maydell 2019-10-04 9:31 ` Stefan Hajnoczi 2019-08-22 11:47 ` [Qemu-devel] " Daniel P. Berrangé 2019-08-22 16:31 ` Dr. David Alan Gilbert 2019-08-22 16:48 ` Paolo Bonzini [this message] 2019-08-22 16:50 ` Dr. David Alan Gilbert 2019-08-22 17:05 ` Paolo Bonzini 2019-08-23 13:15 ` Philippe Mathieu-Daudé 2019-08-24 7:44 ` Alex Bennée 2019-08-22 17:03 ` Daniel P. Berrangé
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=9caf3a64-0841-dde6-3413-a77dc80e22bd@redhat.com \ --to=pbonzini@redhat.com \ --cc=alex.bennee@linaro.org \ --cc=berrange@redhat.com \ --cc=dgilbert@redhat.com \ --cc=kchamart@redhat.com \ --cc=peter.maydell@linaro.org \ --cc=philmd@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=richard.henderson@linaro.org \ --cc=sameo@linux.intel.com \ --cc=stefanha@redhat.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
QEMU-Devel Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/qemu-devel/0 qemu-devel/git/0.git git clone --mirror https://lore.kernel.org/qemu-devel/1 qemu-devel/git/1.git git clone --mirror https://lore.kernel.org/qemu-devel/2 qemu-devel/git/2.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 qemu-devel qemu-devel/ https://lore.kernel.org/qemu-devel \ qemu-devel@nongnu.org public-inbox-index qemu-devel Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.nongnu.qemu-devel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git