From: "Alex Bennée" <alex.bennee@linaro.org>
To: Cleber Rosa <crosa@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Erik Skultety" <eskultet@redhat.com>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Willian Rampazzo" <willianr@redhat.com>,
"Willian Rampazzo" <wrampazz@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [PATCH v7 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI)
Date: Fri, 02 Jul 2021 12:02:04 +0100 [thread overview]
Message-ID: <87wnq9nfm5.fsf@linaro.org> (raw)
In-Reply-To: <20210630012619.115262-1-crosa@redhat.com>
Cleber Rosa <crosa@redhat.com> writes:
> TL;DR: this should allow the QEMU maintainer to push to the staging
> branch, and have custom jobs running on the project's aarch64 and
> s390x machines. Jobs in this version are allowed to fail, to allow
> for the inclusion of the novel machines/jobs without CI disruption.
> Simple usage looks like:
>
> git push remote staging
> ./scripts/ci/gitlab-pipeline-status --verbose --wait
Queued to testing/next, thanks.
--
Alex Bennée
prev parent reply other threads:[~2021-07-02 11:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 1:26 [PATCH v7 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI) Cleber Rosa
2021-06-30 1:26 ` [PATCH v7 1/4] Jobs based on custom runners: documentation and configuration placeholder Cleber Rosa
2021-06-30 1:26 ` [PATCH v7 2/4] Jobs based on custom runners: build environment docs and playbook Cleber Rosa
2021-06-30 10:30 ` Alex Bennée
2021-06-30 18:23 ` Willian Rampazzo
2021-07-01 12:35 ` Alex Bennée
2021-06-30 17:56 ` Willian Rampazzo
2021-06-30 21:51 ` Wainer dos Santos Moschetta
2021-06-30 1:26 ` [PATCH v7 3/4] Jobs based on custom runners: docs and gitlab-runner setup playbook Cleber Rosa
2021-06-30 16:55 ` Willian Rampazzo
2021-06-30 22:02 ` Wainer dos Santos Moschetta
2021-07-01 12:54 ` Alex Bennée
2021-06-30 1:26 ` [PATCH v7 4/4] Jobs based on custom runners: add job definitions for QEMU's machines Cleber Rosa
2021-06-30 22:19 ` Wainer dos Santos Moschetta
2021-07-02 11:02 ` Alex Bennée [this message]
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=87wnq9nfm5.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=eskultet@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@redhat.com \
--cc=wrampazz@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).