From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Oliver Steffen <osteffen@redhat.com>
Cc: devel@edk2.groups.io, afish@apple.com, ardb+tianocore@kernel.org,
bob.c.feng@intel.com, Bret.Barkelew@microsoft.com,
gaoliming@byosoft.com.cn, jiewen.yao@intel.com,
jordan.l.justen@intel.com, michael.d.kinney@intel.com,
quic_llindhol@quicinc.com, ray.ni@intel.com,
sami.mujawar@arm.com, sean.brogan@microsoft.com,
yuwei.chen@intel.com, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH v2 0/4] CI: Use Fedora 35 container for Linux jobs
Date: Wed, 8 Jun 2022 08:25:35 +0200 [thread overview]
Message-ID: <20220608062535.nvqkhfb5y22gaolj@sirius.home.kraxel.org> (raw)
In-Reply-To: <20220607115922.108380-1-osteffen@redhat.com>
Hi,
> The container image provides the required compiler toolchains and Qemu
> for the supported architectures. These are then no longer downloaded at
> runtime, avoiding CI failures due to download errors. This approach also
> makes it easier to switch to other or newer compilers. It makes the CI
> setup independent from the default images that Azure DevOps provides.
It is also easier to reproduce and debug CI problems then. Just pull
and run the container image on your developer workstation.
Acked-by: Gerd Hoffmann <kraxel@redhat.com>
take care,
Gerd
prev parent reply other threads:[~2022-06-08 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 11:59 [PATCH v2 0/4] CI: Use Fedora 35 container for Linux jobs Oliver Steffen
2022-06-07 11:59 ` [PATCH v2 1/4] CI: don't force python verison (Linux only) Oliver Steffen
2022-06-07 11:59 ` [PATCH v2 2/4] CI: add ~/.local/bin to PATH " Oliver Steffen
2022-06-07 11:59 ` [PATCH v2 3/4] CI: Use Fedora 35 container " Oliver Steffen
2022-06-07 11:59 ` [PATCH v2 4/4] BaseTools: Remove ext. gcc dependencies " Oliver Steffen
2022-06-08 6:25 ` Gerd Hoffmann [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-list 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=20220608062535.nvqkhfb5y22gaolj@sirius.home.kraxel.org \
--to=devel@edk2.groups.io \
/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