From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: Re: [PATCH 2/2] .gitlab-ci.d: Make separate collapsible log sections for build and test
Date: Thu, 19 Sep 2024 13:09:01 +0200 [thread overview]
Message-ID: <62e75b8e-e0ed-43a1-9d62-6811e21a481a@redhat.com> (raw)
In-Reply-To: <20240918125449.3125571-3-peter.maydell@linaro.org>
On 18/09/2024 14.54, Peter Maydell wrote:
> GitLab lets a CI job create its own collapsible log sections by
> emitting special escape codes, as documented here:
>
> https://docs.gitlab.com/ee/ci/yaml/script.html#expand-and-collapse-job-log-sections
>
> Use these to make "configure", "build" and "test" separate
> collapsible stages.
>
> As recommended by the GitLab docs, we use some shell which is
> sourced in the CI job to define functions to emit the magic
> lines that start and end sections, to hide the ugliness of
> the printf lines from the log.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2024-09-19 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 12:54 [PATCH 0/2] gitlab-ci: Make separate sections for build and test Peter Maydell
2024-09-18 12:54 ` [PATCH 1/2] .gitlab-ci.d: Split build and test in cross build job templates Peter Maydell
2024-09-19 11:06 ` Thomas Huth
2024-09-18 12:54 ` [PATCH 2/2] .gitlab-ci.d: Make separate collapsible log sections for build and test Peter Maydell
2024-09-19 11:09 ` Thomas Huth [this message]
2024-09-18 14:34 ` [PATCH 0/2] gitlab-ci: Make separate " Richard Henderson
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=62e75b8e-e0ed-43a1-9d62-6811e21a481a@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).