From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com, Tobias <tobias.schaffner@siemens.com>
Subject: Re: [PATCH 1/3] testsuite: Dockerfile for isar-docker image
Date: Thu, 9 Mar 2023 12:07:26 +0100 [thread overview]
Message-ID: <31302d97-8309-89fe-7e09-6fd005815f9a@siemens.com> (raw)
In-Reply-To: <ZAmhPrYxxVpCOPzC@ilbers.de>
On 09.03.23 10:05, Baurzhan Ismagulov wrote:
> Thanks Tobias for the quick review,
>
> On 2023-03-09 07:57, Schaffner, Tobias wrote:
>> Why not choose kas-isar as parent image and just add the CI specific
>> needs? Is there a reason why you want to maintain this a second time?
>
> Our preferred way would actually be to fix specific versions of avocado and (if
> necessary) qemu in the kas-isar image and continue using it. The new image was
> created with the minimal Isar requirements (kas-isar has some 300 MB of
> additional packages). We'll check kas-isar as parent and let you know. We'll
> probably need some sync on it, like user ID handling, which image version will
> be used when, planned updates, etc.
Given that most Isar users are also kas-isar users, it would not be an
elegant decision to create and maintain an own base image for Isar CI
purposes only.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2023-03-09 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 4:36 [PATCH 0/3] Switch to own " Uladzimir Bely
2023-03-07 4:36 ` [PATCH 1/3] testsuite: Dockerfile for " Uladzimir Bely
2023-03-09 7:57 ` Schaffner, Tobias
2023-03-09 9:05 ` Baurzhan Ismagulov
2023-03-09 9:14 ` Uladzimir Bely
2023-03-09 11:10 ` Jan Kiszka
2023-03-09 11:07 ` Jan Kiszka [this message]
2023-03-07 4:36 ` [PATCH 2/3] testsuite: Add README for isar-docker Uladzimir Bely
2023-03-07 4:36 ` [PATCH 3/3] gitlab-ci: Switch to own isar-docker image Uladzimir Bely
2023-03-14 13:49 ` [PATCH 0/3] " Henning Schild
2023-03-14 14:00 ` Jan Kiszka
2023-03-14 14:25 ` Henning Schild
2023-03-14 14:28 ` 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=31302d97-8309-89fe-7e09-6fd005815f9a@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=tobias.schaffner@siemens.com \
/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