From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>,
Uladzimir Bely <ubely@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 0/3] Switch to own isar-docker image
Date: Tue, 14 Mar 2023 15:00:53 +0100 [thread overview]
Message-ID: <75084940-425f-c8df-8d60-aa7a248dce5e@siemens.com> (raw)
In-Reply-To: <20230314144908.75db68dd@md1za8fc.ad001.siemens.net>
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.
Jan
> Henning
>
> Am Tue, 7 Mar 2023 05:36:46 +0100
> schrieb Uladzimir Bely <ubely@ilbers.de>:
>
>> In comparison with previously used kas-isar image, switch to own
>> isar-docker one, that better fit CI needs:
>> - Avocado testsuite preinstalled;
>> - Qemu-system packages for run tests preinstalled;
>> - Potentially, avocado can be run directly, without ci_build.sh.
>>
>> Uladzimir Bely (3):
>> testsuite: Dockerfile for isar-docker image
>> testsuite: Add README for isar-docker
>> gitlab-ci: Switch to own isar-docker image
>>
>> .gitlab-ci.yml | 3 +-
>> testsuite/dockerdata/.dockerignore | 3 +
>> testsuite/dockerdata/Dockerfile | 48 ++++++
>> testsuite/dockerdata/README.md | 19 +++
>> testsuite/dockerdata/container-entrypoint | 9 ++
>> testsuite/dockerdata/contrib/oe-git-proxy | 187
>> ++++++++++++++++++++++ 6 files changed, 268 insertions(+), 1
>> deletion(-) create mode 100644 testsuite/dockerdata/.dockerignore
>> create mode 100644 testsuite/dockerdata/Dockerfile
>> create mode 100644 testsuite/dockerdata/README.md
>> create mode 100755 testsuite/dockerdata/container-entrypoint
>> create mode 100755 testsuite/dockerdata/contrib/oe-git-proxy
>>
>
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2023-03-14 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 4:36 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
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 [this message]
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=75084940-425f-c8df-8d60-aa7a248dce5e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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