From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH 0/2] gitlab: expose installed package info in build logs
Date: Wed, 24 Jul 2024 12:14:36 +0100 [thread overview]
Message-ID: <87o76nvy77.fsf@draig.linaro.org> (raw)
In-Reply-To: <20240724095505.33544-1-berrange@redhat.com> ("Daniel P. Berrangé"'s message of "Wed, 24 Jul 2024 10:55:02 +0100")
Daniel P. Berrangé <berrange@redhat.com> writes:
> Many times we see a build job start failing, we wonder if the installed
> packages have changed since the last passing build. We can rarely
> diagnose this, however, since we only have the new container image, not
> the old one.
>
> The lcitool generated containers create a /packages.txt file whose
> content is intended to be output in the build phase, so record the
> packages associated with the build.
>
> This adds packages.txt to the manually written containers, and modifies
> the build jobs to display this content. This will improve our future
> debuggability of CI problems.
Queued to maintainer/for-9.1, thanks.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2024-07-24 11:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 9:55 [PATCH 0/2] gitlab: expose installed package info in build logs Daniel P. Berrangé
2024-07-24 9:55 ` [PATCH 1/2] gitlab: record installed packages in /packages.txt in containers Daniel P. Berrangé
2024-07-24 9:55 ` [PATCH 2/2] gitlab: display /packages.txt in build jobs Daniel P. Berrangé
2024-07-24 11:14 ` Alex Bennée [this message]
2024-07-25 7:06 ` [PATCH 0/2] gitlab: expose installed package info in build logs Philippe Mathieu-Daudé
2024-07-25 9:42 ` Manos Pitsidianakis
2024-07-25 9:56 ` Thomas Huth
2024-07-25 10:20 ` Manos Pitsidianakis
2024-07-25 10:00 ` Daniel P. Berrangé
2024-07-25 10:14 ` 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=87o76nvy77.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--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).