From: Anthony PERARD <anthony.perard@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Doug Goldstein <cardoe@cardoe.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: [XEN PATCH v3 4/4] automation: Remove non-debug x86_32 build jobs
Date: Fri, 24 Feb 2023 17:29:15 +0000 [thread overview]
Message-ID: <20230224172915.39675-5-anthony.perard@citrix.com> (raw)
In-Reply-To: <20230224172915.39675-1-anthony.perard@citrix.com>
In the interest of having less jobs, we remove the x86_32 build jobs
that do release build. Debug build is very likely to be enough to find
32bit build issues.
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
---
Notes:
v3:
- new patch
Proposed here:
https://lore.kernel.org/r/7ec61260-0fec-25e2-6fa7-ec1d86e8067d@citrix.com
automation/gitlab-ci/build.yaml | 20 --------------------
1 file changed, 20 deletions(-)
diff --git a/automation/gitlab-ci/build.yaml b/automation/gitlab-ci/build.yaml
index 2be1b05d5c..a2891c5937 100644
--- a/automation/gitlab-ci/build.yaml
+++ b/automation/gitlab-ci/build.yaml
@@ -251,21 +251,11 @@ debian-stretch-gcc-debug:
variables:
CONTAINER: debian:stretch
-debian-stretch-32-clang:
- extends: .clang-x86-32-build
- variables:
- CONTAINER: debian:stretch-i386
-
debian-stretch-32-clang-debug:
extends: .clang-x86-32-build-debug
variables:
CONTAINER: debian:stretch-i386
-debian-stretch-32-gcc:
- extends: .gcc-x86-32-build
- variables:
- CONTAINER: debian:stretch-i386
-
debian-stretch-32-gcc-debug:
extends: .gcc-x86-32-build-debug
variables:
@@ -311,21 +301,11 @@ debian-unstable-gcc-debug-randconfig:
CONTAINER: debian:unstable
RANDCONFIG: y
-debian-unstable-32-clang:
- extends: .clang-x86-32-build
- variables:
- CONTAINER: debian:unstable-i386
-
debian-unstable-32-clang-debug:
extends: .clang-x86-32-build-debug
variables:
CONTAINER: debian:unstable-i386
-debian-unstable-32-gcc:
- extends: .gcc-x86-32-build
- variables:
- CONTAINER: debian:unstable-i386
-
debian-unstable-32-gcc-debug:
extends: .gcc-x86-32-build-debug
variables:
--
Anthony PERARD
next prev parent reply other threads:[~2023-02-24 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 17:29 [XEN PATCH v3 0/4] automation: Update containers to allow HTTPS access to xenbits Anthony PERARD
2023-02-24 17:29 ` [XEN PATCH v3 1/4] automation: Use EOL tag for Jessie container Anthony PERARD
2023-02-24 17:29 ` [XEN PATCH v3 2/4] automation: Remove testing on Debian Jessie Anthony PERARD
2023-02-24 17:29 ` [XEN PATCH v3 3/4] automation: Remove expired root certificates used to be used by let's encrypt Anthony PERARD
2023-02-24 17:29 ` Anthony PERARD [this message]
2023-02-24 17:37 ` [XEN PATCH v3 0/4] automation: Update containers to allow HTTPS access to xenbits Andrew Cooper
2023-02-24 18:12 ` Anthony PERARD
2023-02-24 18:22 ` Andrew Cooper
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=20230224172915.39675-5-anthony.perard@citrix.com \
--to=anthony.perard@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.