Re: [PATCH 0/3] Switch to own isar-docker image

[Jan Kiszka <jan.kiszka@siemens.com>]

On 14.03.23 15:25, Henning Schild wrote:
> Am Tue, 14 Mar 2023 15:00:53 +0100
> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> 
>> On 14.03.23 14:49, Henning Schild wrote:
>>> I will not use some container from ilbers. If avocado turns out to
>>> be a problem, we can switch to pytest or something else that is
>>> easy to install. But please not yet another container to cover up
>>> the problems. 
>>
>> To be fair, the test env also needs qemu to run certain tests,
>> irrespective of the test framework. But that is something kas will not
>> include into its build-only containers. So, there is extra
>> installation needed. Or an extra container, but that should be based
>> on kas-isar, not duplicating its base work.
> 
> At the moment we use kas-isar and install the additional things in a
> controlled manner. I do not see the problem with that, except for maybe
> a very neglectable download/install reduction (given what CI does once
> it starts rolling). There are far better places for optimization,
> saving time/bandwidth/storage.
> 
> Of cause kas is not an isar feature and isar can decide on its own
> which container or if to container ... but in the end we at Siemens
> will often combine with kas and its containers, so we will use that
> anyhow ... no matter what the official container will become, kas will
> have to work as well.

Yep, that's exactly why I voted against having an own base container now.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux