Re: [PATCH] gitlab-ci: Use artifacts instead of dumping logs in the Cirrus-CI jobs

[Peter Maydell]

On Wed, 15 Feb 2023 at 15:33, Thomas Huth <thuth@redhat.com> wrote:
>
> On 15/02/2023 15.58, Daniel P. Berrangé wrote:
> > On Wed, Feb 15, 2023 at 03:25:03PM +0100, Thomas Huth wrote:
> >> The meson log files can get very big, especially if running the tests in
> >> verbose mode. So dumping those logs to the console was a bad idea, since
> >> gitlab truncates the output if it is getting too big. Let's publish the
> >> logs as artifacts instead. This has the disadvantage that you have to
> >> look up the logs on cirrus-ci.com now instead, but that's still better
> >> than not having the important part of the log at all since it got
> >> truncated.
> >
> > Having to go over to cirrus-ci.com is pretty awful user experiance,
> > especially as there's no direct link.
>
> It's not that bad, see e.g.:
>
>   https://gitlab.com/thuth/qemu/-/jobs/3775523498
>
> The log shows a link to cirrus-ci.com at the end:
>
>   Build failed: https://cirrus-ci.com/build/4811273133621248
>
> If you click on that URL, you've just got to go into the "build" and click
> through the build artifacts to get to the log that you want.

Could somebody write up some documentation for how to get from
"top level gitlab CI pipeline page" to "detailed logs for a
job failure", please? I'm finding that the UI for this (both
Cirrus and gitlab) is very non-obvious, so a writeup like
the above of "follow this link from the log, click this button,
go look at build artefact X" would be very helpful.
Somewhere in https://wiki.qemu.org/Merges is probably a
convenient place for thsi.

thanks
-- PMM