public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Oliver Steffen" <osteffen@redhat.com>
To: devel@edk2.groups.io
Cc: 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,
	kraxel@redhat.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, Oliver Steffen <osteffen@redhat.com>,
	Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH v2 0/4] CI: Use Fedora 35 container for Linux jobs
Date: Tue,  7 Jun 2022 13:59:18 +0200	[thread overview]
Message-ID: <20220607115922.108380-1-osteffen@redhat.com> (raw)


Update CI, run all Linux (aka Ubuntu-GCC5) bases jobs in custom
containers.

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.

The container images are hosted on ghcr.io and are automatically
generated using GitHub Actions. The Dockerfiles are maintained in the
Tianocore "containers" repository:
https://github.com/tianocore/containers.

The current image is based on Fedora 35, with gcc 11. Fedora was chosen
because of its fast release cycle which makes it easy to keep the
toolchains up-to-date.

Some further possible changes not included in this series:
- Use a stack of layered images. One image for general purpose and
  build-only jobs and one that adds Qemu to the first, for the testing
  job that involve Qemu. This reduces the total download size. This was
  suggested by Chris Fernald. The work in the image side is done, need
  to change the CI setup accordingly.
- Further reduce the number of external dependencies that need to be
  downloaded at runtime. Candidates are iasl and nasm, which are already
  included in the image but not used yet.

PR: https://github.com/tianocore/edk2/pull/2935


v2:
- Images are now hosted under the Tianocore Organization
  https://github.com/tianocore/containers

v1:
- Thread: https://edk2.groups.io/g/devel/message/89058
- Images were hosted at https://github.com/osteffenrh/edk2-build-images

Acked-by: Ard Biesheuvel <ardb@kernel.org>


Oliver Steffen (4):
  CI: don't force python verison (Linux only)
  CI: add ~/.local/bin to PATH (Linux only)
  CI: Use Fedora 35 container (Linux only)
  BaseTools: Remove ext. gcc dependencies (Linux only)

 .../templates/basetools-build-steps.yml       |  9 --------
 .../templates/platform-build-run-steps.yml    |  7 ++++++
 .../templates/pr-gate-build-job.yml           |  3 +++
 .azurepipelines/templates/pr-gate-steps.yml   |  7 ++++++
 .../.azurepipelines/Ubuntu-GCC5.yml           |  6 ++---
 BaseTools/Bin/gcc_aarch64_linux_ext_dep.yaml  | 21 ------------------
 BaseTools/Bin/gcc_arm_linux_ext_dep.yaml      | 21 ------------------
 .../Bin/gcc_riscv64_unknown_ext_dep.yaml      | 22 -------------------
 .../.azurepipelines/Ubuntu-GCC5.yml           |  2 ++
 .../.azurepipelines/Ubuntu-GCC5.yml           |  6 ++---
 10 files changed, 23 insertions(+), 81 deletions(-)
 delete mode 100644 BaseTools/Bin/gcc_aarch64_linux_ext_dep.yaml
 delete mode 100644 BaseTools/Bin/gcc_arm_linux_ext_dep.yaml
 delete mode 100644 BaseTools/Bin/gcc_riscv64_unknown_ext_dep.yaml

-- 
2.36.1


             reply	other threads:[~2022-06-07 11:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 11:59 Oliver Steffen [this message]
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 ` [PATCH v2 0/4] CI: Use Fedora 35 container for Linux jobs Gerd Hoffmann

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=20220607115922.108380-1-osteffen@redhat.com \
    --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