From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject:
Date: Fri, 26 May 2023 07:23:37 +0200 [thread overview]
Message-ID: <20230526052342.7945-1-ubely@ilbers.de> (raw)
Subject: [PATCH v3 0/5] Use `docker-isar` image for maintainer test jobs
This patchset allows to use own `docker-isar` image for maintainer
test jobs that better fits CI needs:
- Avocado testsuite preinstalled;
- Qemu-system packages for run tests preinstalled;
- Potentially, avocado can be run directly, without ci_build.sh.
By default, `kas-isar` image is still used. To use `docker-isar` one,
IMAGE="docker-isar" variable should be set in the schedule settings.
Also, by specifying "TESTSUITE" variable it's now possible to filter
jobs (e.g. select "fast" or "full" or "dev") to be run in the pipeline.
Changes since v2:
- Rebased on latest next.
- Don't use confusing `latest` tag as ancor for image generation command.
Changes since v1:
- Rename patchset from `Switch to own docker-isar image`
- Update to the recent version of `kas-isar` images.
- `docker-isar` image is now based on `kas-isar` one.
- Use `docker-isar` naming in commit messages (in some places
'isar-docker' was used).
- Introduce TESTSUITE and IMAGE variables to control schedules.
Existing GitLab installations that don't use these variables continue
using `kas-isar`.
Uladzimir Bely (5):
testsuite: Dockerfile for docker-isar image
testsuite: Add README for docker-isar
gitlab-ci: Switch to `rules` instead of `except` and `only`
gitlab-ci.yml: Run 'fast' and 'full' only if specific variable set
gitlab-ci.yml: Add jobs that run with custom docker-isar image
.gitlab-ci.yml | 65 ++++++++++++++++++++++++++----
testsuite/dockerdata/.dockerignore | 3 ++
testsuite/dockerdata/Dockerfile | 11 +++++
testsuite/dockerdata/README.md | 20 +++++++++
4 files changed, 92 insertions(+), 7 deletions(-)
create mode 100644 testsuite/dockerdata/.dockerignore
create mode 100644 testsuite/dockerdata/Dockerfile
create mode 100644 testsuite/dockerdata/README.md
--
2.20.1
next reply other threads:[~2023-05-26 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 5:23 Uladzimir Bely [this message]
2023-05-26 5:23 ` [PATCH v3 1/5] testsuite: Dockerfile for docker-isar image Uladzimir Bely
2023-05-26 5:23 ` [PATCH v3 2/5] testsuite: Add README for docker-isar Uladzimir Bely
2023-05-26 5:23 ` [PATCH v3 3/5] gitlab-ci: Switch to `rules` instead of `except` and `only` Uladzimir Bely
2023-05-26 5:23 ` [PATCH v3 4/5] gitlab-ci.yml: Run 'fast' and 'full' only if specific variable set Uladzimir Bely
2023-05-26 5:23 ` [PATCH v3 5/5] gitlab-ci.yml: Add jobs that run with custom docker-isar image Uladzimir Bely
2023-05-26 7:03 ` Uladzimir Bely
2023-06-14 6:03 ` [PATCH v3 0/5] Use `docker-isar` image for maintainer test jobs Uladzimir Bely
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=20230526052342.7945-1-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.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