[PATCH 3/9] GitLab CI: Make wider use of tags
Simon Glass
sjg at chromium.org
Mon Dec 9 16:00:42 CET 2024
Hi Tom,
On Sun, 8 Dec 2024 at 12:08, Tom Rini <trini at konsulko.com> wrote:
>
> First, introduce DEFAULT_ALL_TAG, DEFAULT_ARM64_TAG, DEFAULT_AMD64_TAG
> and DEFAULT_FAST_AMD64_TAG and remove the previous DEFAULT_TAG (as
> anyone making use of that will need to adjust their jobs). This allows
> us to say that some jobs can run on amd64 or arm64 hosts under the all
> tag, while some jobs must run on amd64 (the Xtensa jobs due to
> binary-only toolchains and sandbox for now) Then we rework the world
> build stage to only run on our very fast amd64 hosts, or our arm64 hosts
> (which are also very fast). This should result in a similar overall
> build time but also a much more consistent overall build time as we
> won't have the two big world jobs possibly run on our slower build
> nodes.
>
> Signed-off-by: Tom Rini <trini at konsulko.com>
> ---
> .gitlab-ci.yml | 74 ++++++++++++++++++--------------------------------
> 1 file changed, 27 insertions(+), 47 deletions(-)
I'd prefer fast_amd64 to avoid spaces
What is the run time for this new, unified 'world' build? I just
wonder whether splitting it might make the runs go faster?
Regards,
SImon
More information about the U-Boot
mailing list