From: Juan Quintela <quintela@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Bin Meng" <bmeng.cn@gmail.com>
Subject: Re: [PATCH 0/2] gitlab: improve artifact handling
Date: Tue, 09 May 2023 21:20:40 +0200 [thread overview]
Message-ID: <87ednpb9br.fsf@secure.mitica> (raw)
In-Reply-To: <20230503145535.91325-1-berrange@redhat.com> ("Daniel P. Berrangé"'s message of "Wed, 3 May 2023 15:55:33 +0100")
Daniel P. Berrangé <berrange@redhat.com> wrote:
> We are missing test log artifacts from various check jobs on failure,
> and also missing test logs from the coverage job
>
> Daniel P. Berrangé (2):
> gitlab: explicit set artifacts publishing criteria
> gitlab: ensure coverage job also publishes meson log
>
> .gitlab-ci.d/buildtest-template.yml | 4 +++-
> .gitlab-ci.d/buildtest.yml | 5 +++++
> .gitlab-ci.d/crossbuild-template.yml | 1 +
> .gitlab-ci.d/crossbuilds.yml | 2 ++
> .gitlab-ci.d/custom-runners.yml | 1 +
> .gitlab-ci.d/opensbi.yml | 1 +
> 6 files changed, 13 insertions(+), 1 deletion(-)
Daniel
I love the idea of this series.
But I have no idea about gitlab, yml or gitlab, so my review is
useless.
But thanks for doing it.
Later, Juan.
next prev parent reply other threads:[~2023-05-09 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 14:55 [PATCH 0/2] gitlab: improve artifact handling Daniel P. Berrangé
2023-05-03 14:55 ` [PATCH 1/2] gitlab: explicit set artifacts publishing criteria Daniel P. Berrangé
2023-05-03 14:55 ` [PATCH 2/2] gitlab: ensure coverage job also publishes meson log Daniel P. Berrangé
2023-05-09 19:20 ` Juan Quintela [this message]
2023-05-11 10:47 ` [PATCH 0/2] gitlab: improve artifact handling Alex Bennée
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=87ednpb9br.fsf@secure.mitica \
--to=quintela@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=bmeng.cn@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.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).