From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: [isar-cip-core][PATCH 0/3] ci improvements
Date: Wed, 17 Sep 2025 10:01:03 +0200 [thread overview]
Message-ID: <cover.1758096066.git.jan.kiszka@siemens.com> (raw)
Primarily speeds up lava jobs by using our own container.
Jan
Jan Kiszka (3):
ci: Do not attach cve-checks to scheduled pipelines
ci: Add job to build own lavacli container for tests
ci: Switch test jobs to self-built lavacli container
.gitlab-ci.yml | 22 +++++++++++++++++++---
scripts/Dockerfile.lavacli | 17 +++++++++++++++++
scripts/submit_lava.sh | 2 --
3 files changed, 36 insertions(+), 5 deletions(-)
create mode 100644 scripts/Dockerfile.lavacli
--
2.51.0
next reply other threads:[~2025-09-17 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 8:01 Jan Kiszka [this message]
2025-09-17 8:01 ` [isar-cip-core][PATCH 1/3] ci: Do not attach cve-checks to scheduled pipelines Jan Kiszka
2025-09-17 8:01 ` [isar-cip-core][PATCH 2/3] ci: Add job to build own lavacli container for tests Jan Kiszka
2025-09-17 9:36 ` [cip-dev] " Chris Paterson
2025-09-17 9:42 ` Jan Kiszka
2025-09-17 8:01 ` [isar-cip-core][PATCH 3/3] ci: Switch test jobs to self-built lavacli container 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.1758096066.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