From: Peter Xu <peterx@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 3/3] ci: Reduce the size of artifacts for build-previous-qemu
Date: Wed, 7 May 2025 15:08:15 -0400 [thread overview]
Message-ID: <aBuvnw_GfmkhkKnY@x1.local> (raw)
In-Reply-To: <20250507155835.31074-4-farosas@suse.de>
On Wed, May 07, 2025 at 12:58:35PM -0300, Fabiano Rosas wrote:
> The build-previous-qemu job is intented to produce a build of the
> previous QEMU release for consumption by the migration-compat-*
> jobs. Keep only the pieces of the build that are necessary.
>
> Signed-off-by: Fabiano Rosas <farosas@suse.de>
Reviewed-by: Peter Xu <peterx@redhat.com>
The other thing I'm thinking is maybe we could create migration.yml and
move all migration stuff over, having buildtest.yml include that..
--
Peter Xu
prev parent reply other threads:[~2025-05-07 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 15:58 [PATCH 0/3] migration, ci: Tweaks to migration-compat jobs Fabiano Rosas
2025-05-07 15:58 ` [PATCH 1/3] ci: Re-enable python subtests in qtest migration suite Fabiano Rosas
2025-05-07 18:48 ` Peter Xu
2025-05-07 15:58 ` [PATCH 2/3] ci: Fix build-previous-qemu when the version tag is absent Fabiano Rosas
2025-05-07 19:07 ` Peter Xu
2025-05-07 19:39 ` Fabiano Rosas
2025-05-07 15:58 ` [PATCH 3/3] ci: Reduce the size of artifacts for build-previous-qemu Fabiano Rosas
2025-05-07 19:08 ` Peter Xu [this message]
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=aBuvnw_GfmkhkKnY@x1.local \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--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.