From: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v2 3/6] gitlab: use .base_meson_job_template from crossbuild jobs
Date: Wed, 24 Jun 2026 09:56:53 -0700 [thread overview]
Message-ID: <2a8dd2d8-ebe9-468a-9adc-2545bc37be04@oss.qualcomm.com> (raw)
In-Reply-To: <20260624124657.2725376-4-berrange@redhat.com>
On 6/24/2026 5:46 AM, Daniel P. Berrangé wrote:
> This ensures that crossbuild jobs capture the build/meson-logs
> content as artifacts to aid in debugging.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> .gitlab-ci.d/crossbuild-template.yml | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
Reviewed-by: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
next prev parent reply other threads:[~2026-06-24 16:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 12:46 [PATCH v2 0/6] gitlab: expose more info about CI runner environment as artifacts Daniel P. Berrangé
2026-06-24 12:46 ` [PATCH v2 1/6] gitlab: remove unused .cross_test_artifacts template Daniel P. Berrangé
2026-06-24 13:03 ` Philippe Mathieu-Daudé
2026-06-24 16:56 ` Pierrick Bouvier
2026-06-24 12:46 ` [PATCH v2 2/6] gitlab: move .meson_job_template into base.yaml Daniel P. Berrangé
2026-06-24 16:56 ` Pierrick Bouvier
2026-06-24 12:46 ` [PATCH v2 3/6] gitlab: use .base_meson_job_template from crossbuild jobs Daniel P. Berrangé
2026-06-24 16:56 ` Pierrick Bouvier [this message]
2026-06-24 12:46 ` [PATCH v2 4/6] gitlab: pull ccache setup into .base_meson_ccache_job_template Daniel P. Berrangé
2026-06-24 16:57 ` Pierrick Bouvier
2026-06-24 12:46 ` [PATCH v2 5/6] gitlab: pull before_script logic into .base_meson_job_template Daniel P. Berrangé
2026-06-24 16:58 ` Pierrick Bouvier
2026-06-24 12:46 ` [PATCH v2 6/6] gitlab: greatly expand captured info about CI runner environment Daniel P. Berrangé
2026-06-24 16:58 ` Pierrick Bouvier
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=2a8dd2d8-ebe9-468a-9adc-2545bc37be04@oss.qualcomm.com \
--to=pierrick.bouvier@oss.qualcomm.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.