From: Willian Rampazzo <wrampazz@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v2 10/10] gitlab-ci: Move current job set to qemu-project.yml
Date: Tue, 11 May 2021 17:48:40 -0300 [thread overview]
Message-ID: <CAKJDGDaLRsHm5CwuTynEjtqKuT=Tu5s9UEnBZN0=oqcm48kA-Q@mail.gmail.com> (raw)
In-Reply-To: <20210511072952.2813358-11-f4bug@amsat.org>
On Tue, May 11, 2021 at 4:30 AM Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
>
> To allow forks to easily decide which jobs they want to run,
> but without disrupting the current default, move the current
> set of jobs to a new file corresponding to the jobs run by
> the mainstream project CI:
> https://gitlab.com/qemu-project/qemu/-/pipelines
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> .gitlab-ci.d/qemu-project.yml | 11 +++++++++++
> .gitlab-ci.yml | 8 +-------
> 2 files changed, 12 insertions(+), 7 deletions(-)
> create mode 100644 .gitlab-ci.d/qemu-project.yml
>
Reviewed-by: Willian Rampazzo <willianr@redhat.com>
prev parent reply other threads:[~2021-05-11 20:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 7:29 [PATCH v2 00/10] gitlab-ci: Ease forks pipeline workflow Philippe Mathieu-Daudé
2021-05-11 7:29 ` [PATCH v2 01/10] gitlab-ci: Replace YAML anchors by extends (acceptance_test_job) Philippe Mathieu-Daudé
2021-05-11 20:24 ` Willian Rampazzo
2021-05-11 7:29 ` [PATCH v2 02/10] gitlab-ci: Rename acceptance_test_job -> integration_test_job Philippe Mathieu-Daudé
2021-05-11 7:29 ` [PATCH v2 03/10] gitlab-ci: Extract container job template to container-template.yml Philippe Mathieu-Daudé
2021-05-11 20:26 ` Willian Rampazzo
2021-05-11 7:29 ` [PATCH v2 04/10] gitlab-ci: Extract crossbuild job templates to crossbuild-template.yml Philippe Mathieu-Daudé
2021-05-11 20:27 ` Willian Rampazzo
2021-05-11 7:29 ` [PATCH v2 05/10] gitlab-ci: Extract DCO/style check jobs to static_checks.yml Philippe Mathieu-Daudé
2021-05-11 20:29 ` Willian Rampazzo
2021-05-11 7:29 ` [PATCH v2 06/10] gitlab-ci: Extract build stages to stages.yml Philippe Mathieu-Daudé
2021-05-11 20:32 ` Willian Rampazzo
2021-05-11 7:29 ` [PATCH v2 07/10] gitlab-ci: Extract default build/test jobs templates Philippe Mathieu-Daudé
2021-05-11 20:33 ` Willian Rampazzo
2021-05-11 7:29 ` [PATCH v2 08/10] gitlab-ci: Extract all default build/test jobs to buildtest.yml Philippe Mathieu-Daudé
2021-05-11 20:35 ` Willian Rampazzo
2021-05-11 7:29 ` [PATCH v2 09/10] gitlab-ci: Extract core container jobs to container-core.yml Philippe Mathieu-Daudé
2021-05-11 20:36 ` Willian Rampazzo
2021-05-11 7:29 ` [PATCH v2 10/10] gitlab-ci: Move current job set to qemu-project.yml Philippe Mathieu-Daudé
2021-05-11 20:48 ` Willian Rampazzo [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='CAKJDGDaLRsHm5CwuTynEjtqKuT=Tu5s9UEnBZN0=oqcm48kA-Q@mail.gmail.com' \
--to=wrampazz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--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).