From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH] gitlab-ci: Remove unused container images
Date: Fri, 19 Feb 2021 12:09:50 +0100 [thread overview]
Message-ID: <20210219110950.2308025-1-thuth@redhat.com> (raw)
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.
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:
--
2.27.0
next reply other threads:[~2021-02-19 11:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 11:09 Thomas Huth [this message]
2021-02-19 11:40 ` [PATCH] gitlab-ci: Remove unused container images 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
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=20210219110950.2308025-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.