From: Peter Maydell <peter.maydell@linaro.org>
To: Cleber Rosa <crosa@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Wainer dos Santos Moschetta <wainersm@redhat.com>
Subject: Re: [RFC PATCH 2/2] GitLab CI: crude mapping of PMM's scripts to jobs
Date: Tue, 10 Mar 2020 09:30:22 +0000 [thread overview]
Message-ID: <CAFEAcA9mLypcRgH6qnrcUsWaTL0Tp283M_ZaNaRezhCma8OmiQ@mail.gmail.com> (raw)
In-Reply-To: <20200310050106.GB50141@localhost.localdomain>
On Tue, 10 Mar 2020 at 05:01, Cleber Rosa <crosa@redhat.com> wrote:
> Thanks for the very straight answers here. I'll work
> on those two remaining points (windows cross builds, and
> incremental builds).
I did wonder if incremental build was going to be awkward
to test in a CI setup.
Anyway, I think it would be good to start working with the
basic "do CI this way" framework now, rather than trying
to get all the test configs I have now working with it.
I can always run the builds through the new test setup
and in parallel do the handful of "not yet implemented in
the new setup" builds by hand with the old scripts.
thanks
-- PMM
next prev parent reply other threads:[~2020-03-10 9:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 3:23 [RFC PATCH 1/2] GitLab CI: avoid calling before_scripts on unintended jobs Cleber Rosa
2020-02-03 3:23 ` [RFC PATCH 2/2] GitLab CI: crude mapping of PMM's scripts to jobs Cleber Rosa
2020-02-03 17:36 ` Wainer dos Santos Moschetta
2020-02-07 19:34 ` Cleber Rosa
2020-02-08 13:02 ` Peter Maydell
2020-03-10 5:01 ` Cleber Rosa
2020-03-10 9:30 ` Peter Maydell [this message]
2020-02-06 13:03 ` Philippe Mathieu-Daudé
2020-02-06 13:05 ` Philippe Mathieu-Daudé
2020-03-10 3:53 ` Cleber Rosa
2020-02-06 13:52 ` Wainer dos Santos Moschetta
2020-02-06 13:54 ` Philippe Mathieu-Daudé
2020-02-06 15:13 ` Thomas Huth
2020-02-07 8:37 ` Thomas Huth
2020-02-07 10:05 ` Thomas Huth
2020-02-07 11:08 ` Alex Bennée
2020-02-07 19:59 ` Cleber Rosa
2020-02-07 16:26 ` Peter Maydell
2020-02-07 19:27 ` Cleber Rosa
2020-02-08 12:51 ` Peter Maydell
2020-02-07 19:46 ` Cleber Rosa
2020-02-03 15:26 ` [RFC PATCH 1/2] GitLab CI: avoid calling before_scripts on unintended jobs Wainer dos Santos Moschetta
2020-02-03 16:08 ` Thomas Huth
2020-02-07 20:01 ` 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=CAFEAcA9mLypcRgH6qnrcUsWaTL0Tp283M_ZaNaRezhCma8OmiQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=crosa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).