From: Javi Merino <javi.merino@cloud.com>
To: xen-devel@lists.xenproject.org
Cc: Javi Merino <javi.merino@cloud.com>,
Doug Goldstein <cardoe@cardoe.com>,
Anthony PERARD <anthony.perard@vates.tech>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: [XEN PATCH v2 0/6] automation: Refresh the remaining Debian containers
Date: Wed, 6 Nov 2024 13:05:01 +0000 [thread overview]
Message-ID: <cover.1730743077.git.javi.merino@cloud.com> (raw)
This is v2 of [0], to refresh the remaining Debian 12 containers. The
containers now use heredocs for readability, and use
"apt-get --no-install-recommends" to minimize the installation of
unnecessary packages. All containers except Debian 12 arm64 and
x86_64 run as a normal user. Debian 12 arm64 and x86_64 have been
kept running as root as Stefano asked for it as it would break the
xilinx workers that are currently in flux.
The updated containers have been tested in
https://gitlab.com/xen-project/people/javimerino/xen/-/pipelines/1526520801
Changes since v1[0]:
- In containerfiles, repeat the "LABEL" intruction for each label and
avoid the backslash at the end of lines.
- Use ENV VAR=value consistently in dockerfiles.
- Dropped the patch that moved the Debian 12 arm64 and x86_64
containers to run as a normal user.
- Added a patch to drop the "-y" in "apt-get update"
- Move libnl-3-dev to the libxl section in the Debian 12 x86_64
dockerfile.
- Add missing requires for libxenguest dombuilder in the Debian 12
x86_64 dockerfile
- Move the expect dependency to the section for tests
[0] https://lore.kernel.org/xen-devel/cover.1729760501.git.javi.merino@cloud.com
Javi Merino (6):
CI: Refresh the Debian 12 x86_64 container
CI: Refresh the Debian 12 x86_32 container
CI: Refresh the Debian 12 arm64 container
CI: Refresh the Debian 12 arm32 cross compile container
CI: Refresh the Debian 12 cppcheck container
CI: Don't use -y with apt-get update
automation/build/debian/11-ppc64le.dockerfile | 2 +-
automation/build/debian/11-riscv64.dockerfile | 2 +-
.../debian/12-arm64v8-arm32-gcc.dockerfile | 28 +++++++
.../debian/12-arm64v8-cppcheck.dockerfile | 79 +++++++++++++++++++
automation/build/debian/12-arm64v8.dockerfile | 68 ++++++++++++++++
automation/build/debian/12-ppc64le.dockerfile | 2 +-
automation/build/debian/12-riscv64.dockerfile | 2 +-
automation/build/debian/12-x86_32.dockerfile | 50 ++++++++++++
.../build/debian/12-x86_64-gcc-ibt.dockerfile | 4 +-
automation/build/debian/12-x86_64.dockerfile | 71 +++++++++++++++++
.../bookworm-arm64v8-arm32-gcc.dockerfile | 24 ------
.../build/debian/bookworm-arm64v8.dockerfile | 55 -------------
.../build/debian/bookworm-cppcheck.dockerfile | 54 -------------
.../build/debian/bookworm-i386.dockerfile | 50 ------------
automation/build/debian/bookworm.dockerfile | 57 -------------
.../build/ubuntu/16.04-x86_64.dockerfile | 2 +-
.../build/ubuntu/18.04-x86_64.dockerfile | 2 +-
.../build/ubuntu/20.04-x86_64.dockerfile | 2 +-
.../build/ubuntu/22.04-x86_64.dockerfile | 2 +-
.../build/ubuntu/24.04-x86_64.dockerfile | 2 +-
automation/gitlab-ci/build.yaml | 68 ++++++++--------
automation/gitlab-ci/test.yaml | 32 ++++----
automation/scripts/containerize | 10 +--
23 files changed, 362 insertions(+), 306 deletions(-)
create mode 100644 automation/build/debian/12-arm64v8-arm32-gcc.dockerfile
create mode 100644 automation/build/debian/12-arm64v8-cppcheck.dockerfile
create mode 100644 automation/build/debian/12-arm64v8.dockerfile
create mode 100644 automation/build/debian/12-x86_32.dockerfile
create mode 100644 automation/build/debian/12-x86_64.dockerfile
delete mode 100644 automation/build/debian/bookworm-arm64v8-arm32-gcc.dockerfile
delete mode 100644 automation/build/debian/bookworm-arm64v8.dockerfile
delete mode 100644 automation/build/debian/bookworm-cppcheck.dockerfile
delete mode 100644 automation/build/debian/bookworm-i386.dockerfile
delete mode 100644 automation/build/debian/bookworm.dockerfile
--
2.45.2
next reply other threads:[~2024-11-06 13:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 13:05 Javi Merino [this message]
2024-11-06 13:05 ` [XEN PATCH v2 1/6] CI: Refresh the Debian 12 x86_64 container Javi Merino
2024-11-06 15:59 ` Andrew Cooper
2024-11-06 13:05 ` [XEN PATCH v2 2/6] CI: Refresh the Debian 12 x86_32 container Javi Merino
2024-11-06 19:13 ` Andrew Cooper
2024-11-06 13:05 ` [XEN PATCH v2 3/6] CI: Refresh the Debian 12 arm64 container Javi Merino
2024-11-06 16:23 ` Stefano Stabellini
2025-03-04 14:09 ` Andrew Cooper
2024-11-06 13:05 ` [XEN PATCH v2 4/6] CI: Refresh the Debian 12 arm32 cross compile container Javi Merino
2024-11-06 13:05 ` [XEN PATCH v2 5/6] CI: Refresh the Debian 12 cppcheck container Javi Merino
2024-11-06 13:05 ` [XEN PATCH v2 6/6] CI: Don't use -y with apt-get update Javi Merino
2024-11-06 15:56 ` 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=cover.1730743077.git.javi.merino@cloud.com \
--to=javi.merino@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--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.