Skip to content

Enable arm64 host support in Gitlab

Tom Rini u-boot 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest9 patches 13 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/9Docker/CI: Only test Xtensa on amd64 hosts.gitlab-ci.yml tools/docker/Dockerfile+10 -22 replies
2/9docker: Use ${TCVER} more widelytools/docker/Dockerfile+26 -261 reply
3/9GitLab CI: Make wider use of tags.gitlab-ci.yml+27 -472 replies
4/9GitLab: Add a default workflow stanza.gitlab-ci.yml+4 -01 reply
5/9Gitlab: Avoid downloading all artifacts in later stages.gitlab-ci.yml+2 -01 reply
6/9docker: Ensure we use the cross toolchain for aarch64 on arm64tools/docker/Dockerfile+3 -01 reply
7/9docker: Prefer the kernelorg toolchains over "root"tools/docker/Dockerfile+2 -21 reply
8/9doc: Expand what we say about building the docker container a bitdoc/build/docker.rst+14 -61 reply
9/9docker: Update to latest "Jammy" tag.azure-pipelines.yml .gitlab-ci.yml tools/docker/Dockerfile+3 -33 replies

Reviews trailers per patch

8 of 9 patches have a Reviewed-by or Acked-by.

PatchSimon Glass
1/9R-b
2/9R-b
3/9
4/9R-b
5/9R-b
6/9R-b
7/9R-b
8/9R-b
9/9R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/9] Enable arm64 host support in Gitlab

Hey all,

First, thanks to Simon Glass and also Linaro, we now have access to a few fast arm64 host machines in our Gitlab instance, to use as CI runners. This series finishes the work that I pushed earlier and Simon had started that enables arm64 hosts to be used for most things now.

The first notable change, especially if you use this on your own Gitlab instance is that "DEFAULT_TAG" is now unused and we instead have:
- DEFAULT_ALL_TAG:
- DEFAULT_ARM64_TAG:
- DEFAULT_AMD64_TAG:
- DEFAULT_FAST_AMD64_TAG:

This lets us say that some jobs can be run on all runners, because they are small enough that anything we'd connect to CI is fast enough and it also does not depend on the underlying host architecture. Next we have tags for any arm64 host, or any amd64 host. Finally, we have a tag for fast amd64 hosts. What these last three are for is that we have a few jobs that need to run on amd64 hosts and so we have to restrict them there, but we also have now reworked the world build jobs to build (almost) everything in a single job and on the fast amd64 machines this is still as quick as the old way was, in practice.

To reach this point, we say that the Xtensa jobs can only run on amd64 hosts. Our targets only work with the binary-only toolchain and so this is a reasonable limit and we exclude them from the world build jobs. We also need to deal with ensuring the right toolchain is used regardless what the host architecture is and that we don't use the host toolchain by accident. Finally, because some of these changes needed to be worked out in the linter, fix some of the general warnings that notes as well.

Signature · 1 line
Tom