qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cleber Rosa <crosa@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Jeff Nelson" <jen@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Ademar Reis" <areis@redhat.com>
Subject: Re: [RFC] QEMU Gating CI
Date: Tue, 21 Jan 2020 15:00:19 -0500	[thread overview]
Message-ID: <20200121200019.GA22131@localhost.localdomain> (raw)
In-Reply-To: <CAFEAcA--Rag8JzvPP+Pvkebv1ifeZkpcx7zSXdDBkpZWmpZwxQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1986 bytes --]

On Fri, Jan 17, 2020 at 02:33:54PM +0000, Peter Maydell wrote:
> On Mon, 2 Dec 2019 at 14:06, Cleber Rosa <crosa@redhat.com> wrote:
> >
> > RFC: QEMU Gating CI
> > ===================
> >
> > This RFC attempts to address most of the issues described in
> > "Requirements/GatinCI"[1].  An also relevant write up is the "State of
> > QEMU CI as we enter 4.0"[2].
> >
> > The general approach is one to minimize the infrastructure maintenance
> > and development burden, leveraging as much as possible "other people's"
> > infrastructure and code.  GitLab's CI/CD platform is the most relevant
> > component dealt with here.
> 
> Happy New Year! Now we're in 2020, any chance of an update on
> plans/progress here? I would very much like to be able to hand
> processing of pull requests over to somebody else after the
> 5.0 cycle, if not before. (I'm quite tempted to make that a
> hard deadline and just say that somebody else will have to
> pick it up for 5.1, regardless...)
> 
> thanks
> -- PMM
> 

Hi Peter,

Happy New Year too!

As an status update, I have some work queued up related to this work
that I need to do some minor polishing and then post to the mailing
list.  That has to do with the changes to container definition files,
and the most basic changes to the GitLab YAML configuration files to
achieve a first stage of implementation.

We'd also have to coordinate access to the existing machines in use,
so that we can validate that this proposal will work.  Just to be
extra clear, I'm available to this initial configuration on the
machines that are currently running the tests, provided you think it's
a good idea.  Also, that would also be helpful to me, as I'm learning
a lot of this stuff as I go, and there's always some tricky new
details on different environments.

PS: I'm actually on the road, but I should be settle by Tomorrow, and
I expect to resume work on this the following day.

Best Regards,
- Cleber.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-01-21 20:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 14:05 [RFC] QEMU Gating CI Cleber Rosa
2019-12-02 17:00 ` Stefan Hajnoczi
2019-12-02 17:08   ` Peter Maydell
2019-12-02 18:28     ` Cleber Rosa
2019-12-02 18:36       ` Warner Losh
2019-12-02 22:38         ` Cleber Rosa
2019-12-02 18:12   ` Cleber Rosa
2019-12-03 14:14     ` Stefan Hajnoczi
2019-12-03 14:07 ` Alex Bennée
2019-12-04  8:55   ` Thomas Huth
2019-12-06 19:03   ` Cleber Rosa
2019-12-03 17:54 ` Peter Maydell
2019-12-05  5:05   ` Cleber Rosa
2020-01-17 14:33 ` Peter Maydell
2020-01-21 20:00   ` Cleber Rosa [this message]
2020-02-03  3:27   ` Cleber Rosa
2020-02-03 15:00     ` Cleber Rosa
2020-02-07 16:42     ` Peter Maydell
2020-02-07 20:38       ` Cleber Rosa
2020-02-08 13:08         ` Peter Maydell
2020-03-02 15:27           ` Peter Maydell
2020-03-05  6:50             ` Cleber Rosa

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=20200121200019.GA22131@localhost.localdomain \
    --to=crosa@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=areis@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jen@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wainersm@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
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;
as well as URLs for NNTP newsgroup(s).