From: Michal Orzel <michal.orzel@amd.com>
To: <xen-devel@lists.xenproject.org>
Cc: Michal Orzel <michal.orzel@amd.com>,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: [PATCH 4/9] automation: Add Arm containers to containerize script
Date: Thu, 22 Sep 2022 15:40:53 +0200 [thread overview]
Message-ID: <20220922134058.1410-5-michal.orzel@amd.com> (raw)
In-Reply-To: <20220922134058.1410-1-michal.orzel@amd.com>
Script automation/scripts/containerize makes it easy to build Xen within
predefined containers from gitlab container registry. However, it is
currently not possible to use it with Arm containers because they are not
listed in the script. Populate the necessary entries.
Signed-off-by: Michal Orzel <michal.orzel@amd.com>
---
automation/scripts/containerize | 3 +++
1 file changed, 3 insertions(+)
diff --git a/automation/scripts/containerize b/automation/scripts/containerize
index 9d4beca4fa4b..0f4645c4cccb 100755
--- a/automation/scripts/containerize
+++ b/automation/scripts/containerize
@@ -25,6 +25,7 @@ die() {
BASE="registry.gitlab.com/xen-project/xen"
case "_${CONTAINER}" in
_alpine) CONTAINER="${BASE}/alpine:3.12" ;;
+ _alpine-arm64v8) CONTAINER="${BASE}/alpine:3.12-arm64v8" ;;
_archlinux|_arch) CONTAINER="${BASE}/archlinux:current" ;;
_riscv64) CONTAINER="${BASE}/archlinux:riscv64" ;;
_centos7) CONTAINER="${BASE}/centos:7" ;;
@@ -35,6 +36,8 @@ case "_${CONTAINER}" in
_stretch|_) CONTAINER="${BASE}/debian:stretch" ;;
_buster-gcc-ibt) CONTAINER="${BASE}/debian:buster-gcc-ibt" ;;
_unstable|_) CONTAINER="${BASE}/debian:unstable" ;;
+ _unstable-arm32-gcc) CONTAINER="${BASE}/debian:unstable-arm32-gcc" ;;
+ _unstable-arm64v8) CONTAINER="${BASE}/debian:unstable-arm64v8" ;;
_trusty) CONTAINER="${BASE}/ubuntu:trusty" ;;
_xenial) CONTAINER="${BASE}/ubuntu:xenial" ;;
_opensuse-leap|_leap) CONTAINER="${BASE}/suse:opensuse-leap" ;;
--
2.25.1
next prev parent reply other threads:[~2022-09-22 13:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 13:40 [PATCH 0/9] GitLab CI cleanup & improvements for Arm Michal Orzel
2022-09-22 13:40 ` [PATCH 1/9] automation: Use custom build jobs when extra config options are needed Michal Orzel
2022-09-22 21:40 ` Stefano Stabellini
2022-09-23 1:27 ` Henry Wang
2022-09-23 7:28 ` Michal Orzel
2022-09-23 22:10 ` Stefano Stabellini
2022-09-22 13:40 ` [PATCH 2/9] automation: Add randconfig build jobs for arm64 alpine container Michal Orzel
2022-09-22 21:42 ` Stefano Stabellini
2022-09-23 7:33 ` Michal Orzel
2022-09-22 13:40 ` [PATCH 3/9] automation: Add debug versions of Arm tests Michal Orzel
2022-09-22 21:53 ` Stefano Stabellini
2022-09-23 7:44 ` Michal Orzel
2022-09-23 22:11 ` Stefano Stabellini
2022-09-22 13:40 ` Michal Orzel [this message]
2022-09-22 22:03 ` [PATCH 4/9] automation: Add Arm containers to containerize script Stefano Stabellini
2022-09-23 13:56 ` Anthony PERARD
2022-09-23 16:54 ` Michal Orzel
2022-09-23 22:23 ` Stefano Stabellini
2022-09-26 13:33 ` Anthony PERARD
2022-09-22 13:40 ` [PATCH 5/9] automation: qemu-smoke-arm32.sh: Modify script to use ImageBuilder Michal Orzel
2022-09-22 22:13 ` Stefano Stabellini
2022-09-23 8:04 ` Michal Orzel
2022-09-23 22:12 ` Stefano Stabellini
2022-09-22 13:40 ` [PATCH 6/9] automation: qemu-alpine-arm64: Cleanup and fixes Michal Orzel
2022-09-22 22:17 ` Stefano Stabellini
2022-09-22 13:40 ` [PATCH 7/9] automation: Rename qemu-smoke-arm64.sh to qemu-smoke-dom0less-arm64.sh Michal Orzel
2022-09-22 22:18 ` Stefano Stabellini
2022-09-22 13:40 ` [PATCH 8/9] automation: Rename qemu-alpine-arm64.sh to qemu-smoke-dom0-arm64.sh Michal Orzel
2022-09-22 22:18 ` Stefano Stabellini
2022-09-22 13:40 ` [PATCH 9/9] automation: Rename qemu-smoke-arm32.sh to qemu-smoke-dom0-arm32.sh Michal Orzel
2022-09-22 22:18 ` Stefano Stabellini
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=20220922134058.1410-5-michal.orzel@amd.com \
--to=michal.orzel@amd.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 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).