CIP-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: [isar-cip-core][PATCH 00/14] CI changes to move testing to trixie
Date: Tue,  2 Dec 2025 10:21:05 +0100	[thread overview]
Message-ID: <cover.1764667279.git.jan.kiszka@siemens.com> (raw)

Quite a lot of changes were needed to finally get us to trixie by
default for testing isar-cip-core.

Along that, I also looked into how to generate lava test images (patches
9 and 10) and refactored the artifact deployment a bit (patch 11).
Please double-check if those changes make sense and are fully correct.

Jan

Jan Kiszka (14):
  tests: Avoid hard-coding distribution in M-COM test
  ci: Prepare for running non-bookworm secure boot tests
  ci: Select qemu-amd64 OVMF according to target release
  ci: Raise qemu x86 CPU model
  qemu-amd64: Raise boot watchdog timeout to 120 seconds
  ci: Inject image version into common cip-core-image.inc
  ci: Clean up no-kernel deployment
  Kconfig: Do not offer swupdate or security options without a kernel
  kas: Auto-enable targz format for kernelci images
  ci: Combine targz with no_kernel option
  ci: Make deployment opt-in
  ci: submit_lava.sh: Reduce number of sed calls
  ci: Build and deploy kernel-panic update artifact
  ci: Switch to trixie based builds and tests

 .gitlab-ci.yml                                | 141 ++++++++++--------
 .reproducible-check-ci.yml                    |   5 +-
 Kconfig                                       |   2 +-
 conf/machine/qemu-amd64.conf                  |   3 +
 kas/opt/kernelci.yml                          |   3 +
 scripts/deploy-cip-core.sh                    |  20 +--
 scripts/submit_lava.sh                        | 102 +++++++------
 .../templates/swupdate-test-action-M-COM.yml  |   2 +-
 8 files changed, 153 insertions(+), 125 deletions(-)

-- 
2.51.0



             reply	other threads:[~2025-12-02  9:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02  9:21 Jan Kiszka [this message]
2025-12-02  9:21 ` [isar-cip-core][PATCH 01/14] tests: Avoid hard-coding distribution in M-COM test Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 02/14] ci: Prepare for running non-bookworm secure boot tests Jan Kiszka
2025-12-02  9:44   ` [cip-dev] " Florian Bezdeka
2025-12-02  9:48     ` Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 03/14] ci: Select qemu-amd64 OVMF according to target release Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 04/14] ci: Raise qemu x86 CPU model Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 05/14] qemu-amd64: Raise boot watchdog timeout to 120 seconds Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 06/14] ci: Inject image version into common cip-core-image.inc Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 07/14] ci: Clean up no-kernel deployment Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 08/14] Kconfig: Do not offer swupdate or security options without a kernel Jan Kiszka
2025-12-02  9:55   ` [cip-dev] " Florian Bezdeka
2025-12-02 10:02     ` Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 09/14] kas: Auto-enable targz format for kernelci images Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 10/14] ci: Combine targz with no_kernel option Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 11/14] ci: Make deployment opt-in Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 12/14] ci: submit_lava.sh: Reduce number of sed calls Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 13/14] ci: Build and deploy kernel-panic update artifact Jan Kiszka
2025-12-02  9:21 ` [isar-cip-core][PATCH 14/14] ci: Switch to trixie based builds and tests Jan Kiszka

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.1764667279.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.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