From: Zhihang Wei <wzh@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
Cedric Hombourger <cedric.hombourger@siemens.com>
Subject: Re: [PATCH 5/9] ci: Add github workflow for building and deploying test-container
Date: Fri, 22 May 2026 12:19:09 +0200 [thread overview]
Message-ID: <be315930-58fa-4d8f-9c61-cd6a320c0123@ilbers.de> (raw)
In-Reply-To: <0d31a55008c43a72c8afcba35319ddb894c49012.1774254639.git.jan.kiszka@siemens.com>
On 3/23/26 09:30, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Trigger a container build if the registery does not yet contain the
> version of the test-container described by testsuite/dockerdata/version.
>
> This obsoletes the need for manual build and deployment. Drop the
> related README.md.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> .github/workflows/main.yml | 72 ++++++++++++++++++++++++++++++++++
> testsuite/dockerdata/README.md | 22 -----------
> 2 files changed, 72 insertions(+), 22 deletions(-)
> create mode 100644 .github/workflows/main.yml
> delete mode 100644 testsuite/dockerdata/README.md
>
> diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
> new file mode 100644
> index 00000000..e9dd039e
> --- /dev/null
> +++ b/.github/workflows/main.yml
> @@ -0,0 +1,72 @@
> +# Copyright (c) Siemens AG, 2026
> +# SPDX-License-Identifier: MIT
> +
> +name: CI
> +
> +on: [push]
> +
> +env:
> + CONTAINER_BASENAME: ${{ vars.CONTAINER_BASENAME || 'ghcr.io/ilbers/isar' }}
> +
> +jobs:
> + container:
> + name: Refresh test-container
> + runs-on: ubuntu-latest
> + permissions:
> + id-token: write
> + packages: write
> + contents: read
> + attestations: write
> + artifact-metadata: write
> + if: github.ref == 'refs/heads/next'
> + steps:
> + - name: Check out repo
> + uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
> +
> + - name: Check for pre-existing container version
> + run: |
> + TEST_CONTAINER_VERSION=$(cat testsuite/dockerdata/version)
> + echo "TEST_CONTAINER_VERSION=$TEST_CONTAINER_VERSION" >> $GITHUB_ENV
Hi,
To trigger a new build of this test-container image, we need to increase the
number in testsuite/dockerdata/version, right?
> + if ! docker manifest inspect ${CONTAINER_BASENAME}/test-container:$TEST_CONTAINER_VERSION >/dev/null 2>&1; then
> + eval $(grep "^KAS_CONTAINER_SCRIPT_VERSION=" kas/kas-container)
> + echo "KAS_VERSION=$KAS_CONTAINER_SCRIPT_VERSION" >> $GITHUB_ENV
How about tagging the test-container image with the same version number as
$KAS_CONTAINER_SCRIPT_VERSION? The current docker-isar image already
does this.
Other than this, we have tested p1-p8 and LGTM.
Zhihang
> + echo "BUILD_CONTAINER=true" >> $GITHUB_ENV
> + fi
> +
> + - name: Set up QEMU
> + uses: docker/setup-qemu-action@ce360397dd3f832beb865e1373c09c0e9f86d70a # v4.0.0
> + with:
> + platforms: linux/amd64,linux/arm64
> + if: ${{ env.BUILD_CONTAINER }}
> + - name: Set up Docker Buildx
> + uses: docker/setup-buildx-action@4d04d5d9486b7bd6fa91e7baf45bbb4f8b9deedd # v4.0.0
> + if: ${{ env.BUILD_CONTAINER }}
> + - name: Login to ghcr.io
> + uses: docker/login-action@b45d80f862d83dbcd57f89517bcf500b2ab88fb2 # v4.0.0
> + with:
> + registry: ghcr.io
> + username: ${{ github.actor }}
> + password: ${{ secrets.GITHUB_TOKEN }}
> + if: ${{ env.BUILD_CONTAINER }}
> +
> + - name: Build and deploy container
> + uses: docker/build-push-action@d08e5c354a6adb9ed34480a06d141179aa583294 #v7.0.0
> + id: push
> + with:
> + platforms: linux/amd64,linux/arm64
> + file: testsuite/dockerdata/Dockerfile
> + build-args: KAS_VERSION=${{ env.KAS_VERSION }}
> + provenance: false
> + outputs: type=registry
> + tags: |
> + ${{ env.CONTAINER_BASENAME }}/test-container:latest
> + ${{ env.CONTAINER_BASENAME }}/test-container:${{ env.TEST_CONTAINER_VERSION }}
> + annotations: ${{ env.DOCKER_METADATA_OUTPUT_ANNOTATIONS }}
> + if: ${{ env.BUILD_CONTAINER }}
> + - name: Attest container image
> + uses: actions/attest@59d89421af93a897026c735860bf21b6eb4f7b26 # v4.1.0
> + with:
> + subject-name: ${{ env.CONTAINER_BASENAME }}/test-container
> + subject-digest: ${{ steps.push.outputs.digest }}
> + push-to-registry: true
> + if: ${{ env.BUILD_CONTAINER }}
> diff --git a/testsuite/dockerdata/README.md b/testsuite/dockerdata/README.md
> deleted file mode 100644
> index 54a78187..00000000
> --- a/testsuite/dockerdata/README.md
> +++ /dev/null
> @@ -1,22 +0,0 @@
> -# Creating image
> -
> -- Make sure `testsuite/dockerdata/version` is bumped for new images, also
> - after updating `kas/kas-container`.
> -
> -- Run:
> -
> -```
> -testsuite/dockerdata/build.sh
> -```
> -
> -# Pushing the image to docker hub
> -
> -- Configure github token (classic) with `write:packages` permissions.
> -
> -- Use it for uploading docker image:
> -
> -```
> -docker push ghcr.io/ilbers/isar/test-container:$(cat testsuite/dockerdata/version)
> -```
> -
> -- Make the uploaded package public
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/be315930-58fa-4d8f-9c61-cd6a320c0123%40ilbers.de.
next prev parent reply other threads:[~2026-05-22 10:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 8:30 [PATCH 0/9] Improve testsuite executability, basic GitHub CI 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 1/9] Update kas-container to 5.2 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 2/9] testsuite: Provide a new kas-based test container and wrapper script 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 3/9] testsuite: Install avocado-framework-plugin-varianter-yaml-to-mux in test-container 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 4/9] testsuite: Add squid to test-container 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 5/9] ci: Add github workflow for building and deploying test-container 'Jan Kiszka' via isar-users
2026-05-22 10:19 ` Zhihang Wei [this message]
2026-05-22 11:03 ` 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 6/9] ci: Switch gitlab-ci to new test-container 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 7/9] CONTRIBUTING: Switch to new run-tests.sh 'Jan Kiszka' via isar-users
2026-03-26 17:01 ` Zhihang Wei
2026-03-26 18:41 ` 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 8/9] testsuite: Drop KFAIL from trixie tests 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 9/9] ci: Add github test job to github workflow 'Jan Kiszka' via isar-users
2026-05-07 8:27 ` [PATCH 0/9] Improve testsuite executability, basic GitHub CI 'MOESSBAUER, Felix' via isar-users
2026-05-07 8:54 ` Zhihang Wei
2026-05-27 8:40 ` Zhihang Wei
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=be315930-58fa-4d8f-9c61-cd6a320c0123@ilbers.de \
--to=wzh@ilbers.de \
--cc=cedric.hombourger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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