From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] gitlab-ci: Remove unused container images
Date: Sat, 20 Feb 2021 21:10:52 +0000 [thread overview]
Message-ID: <87wnv2jvg3.fsf@linaro.org> (raw)
In-Reply-To: <20210219110950.2308025-1-thuth@redhat.com>
Thomas Huth <thuth@redhat.com> writes:
> We're building a lot of containers in the gitlab-CI that we never use.
> This takes away network bandwidth and CPU time from other jobs for no
> use, so let's remove them for now. The individual containers could be
> re-added later when we really need them.
They are used - when people run check-tcg their builds are cached via
gitlab.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> .gitlab-ci.d/containers.yml | 92 -------------------------------------
> 1 file changed, 92 deletions(-)
>
> diff --git a/.gitlab-ci.d/containers.yml b/.gitlab-ci.d/containers.yml
> index 90fac85ce4..233d34c59b 100644
> --- a/.gitlab-ci.d/containers.yml
> +++ b/.gitlab-ci.d/containers.yml
> @@ -53,13 +53,6 @@ amd64-debian11-container:
> variables:
> NAME: debian11
>
> -alpha-debian-cross-container:
> - <<: *container_job_definition
> - stage: containers-layer2
> - needs: ['amd64-debian10-container']
> - variables:
> - NAME: debian-alpha-cross
> -
> amd64-debian-cross-container:
> <<: *container_job_definition
> stage: containers-layer2
> @@ -88,13 +81,6 @@ arm64-debian-cross-container:
> variables:
> NAME: debian-arm64-cross
>
> -arm64-test-debian-cross-container:
> - <<: *container_job_definition
> - stage: containers-layer2
> - needs: ['amd64-debian11-container']
> - variables:
> - NAME: debian-arm64-test-cross
> -
> armel-debian-cross-container:
> <<: *container_job_definition
> stage: containers-layer2
> @@ -109,27 +95,6 @@ armhf-debian-cross-container:
> variables:
> NAME: debian-armhf-cross
>
> -hppa-debian-cross-container:
> - <<: *container_job_definition
> - stage: containers-layer2
> - needs: ['amd64-debian10-container']
> - variables:
> - NAME: debian-hppa-cross
> -
> -m68k-debian-cross-container:
> - <<: *container_job_definition
> - stage: containers-layer2
> - needs: ['amd64-debian10-container']
> - variables:
> - NAME: debian-m68k-cross
> -
> -mips64-debian-cross-container:
> - <<: *container_job_definition
> - stage: containers-layer2
> - needs: ['amd64-debian10-container']
> - variables:
> - NAME: debian-mips64-cross
> -
> mips64el-debian-cross-container:
> <<: *container_job_definition
> stage: containers-layer2
> @@ -151,20 +116,6 @@ mipsel-debian-cross-container:
> variables:
> NAME: debian-mipsel-cross
>
> -powerpc-debian-cross-container:
> - <<: *container_job_definition
> - stage: containers-layer2
> - needs: ['amd64-debian10-container']
> - variables:
> - NAME: debian-powerpc-cross
> -
> -ppc64-debian-cross-container:
> - <<: *container_job_definition
> - stage: containers-layer2
> - needs: ['amd64-debian10-container']
> - variables:
> - NAME: debian-ppc64-cross
> -
> ppc64el-debian-cross-container:
> <<: *container_job_definition
> stage: containers-layer2
> @@ -172,13 +123,6 @@ ppc64el-debian-cross-container:
> variables:
> NAME: debian-ppc64el-cross
>
> -riscv64-debian-cross-container:
> - <<: *container_job_definition
> - stage: containers-layer2
> - needs: ['amd64-debian10-container']
> - variables:
> - NAME: debian-riscv64-cross
> -
> s390x-debian-cross-container:
> <<: *container_job_definition
> stage: containers-layer2
> @@ -186,37 +130,6 @@ s390x-debian-cross-container:
> variables:
> NAME: debian-s390x-cross
>
> -sh4-debian-cross-container:
> - <<: *container_job_definition
> - stage: containers-layer2
> - needs: ['amd64-debian10-container']
> - variables:
> - NAME: debian-sh4-cross
> -
> -sparc64-debian-cross-container:
> - <<: *container_job_definition
> - stage: containers-layer2
> - needs: ['amd64-debian10-container']
> - variables:
> - NAME: debian-sparc64-cross
> -
> -tricore-debian-cross-container:
> - <<: *container_job_definition
> - stage: containers-layer2
> - needs: ['amd64-debian10-container']
> - variables:
> - NAME: debian-tricore-cross
> -
> -xtensa-debian-cross-container:
> - <<: *container_job_definition
> - variables:
> - NAME: debian-xtensa-cross
> -
> -cris-fedora-cross-container:
> - <<: *container_job_definition
> - variables:
> - NAME: fedora-cris-cross
> -
> amd64-fedora-container:
> <<: *container_job_definition
> variables:
> @@ -237,11 +150,6 @@ win64-fedora-cross-container:
> variables:
> NAME: fedora-win64-cross
>
> -amd64-ubuntu1804-container:
> - <<: *container_job_definition
> - variables:
> - NAME: ubuntu1804
> -
> amd64-ubuntu2004-container:
> <<: *container_job_definition
> variables:
--
Alex Bennée
next prev parent reply other threads:[~2021-02-20 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 11:09 [PATCH] gitlab-ci: Remove unused container images Thomas Huth
2021-02-19 11:40 ` Daniel P. Berrangé
2021-02-19 12:00 ` Philippe Mathieu-Daudé
2021-02-19 12:08 ` Daniel P. Berrangé
2021-02-19 13:10 ` Thomas Huth
2021-02-19 13:41 ` Philippe Mathieu-Daudé
2021-02-20 21:11 ` Alex Bennée
2021-02-20 21:10 ` Alex Bennée [this message]
2021-02-21 8:39 ` Philippe Mathieu-Daudé
2021-02-22 5:31 ` Thomas Huth
2021-02-22 8:44 ` Alex Bennée
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=87wnv2jvg3.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).