Skip to content

ci: fih: allow to configure container registry for fih docker image - #2787

Open
tpambor wants to merge 1 commit into
mcu-tools:mainfrom
tpambor:ci-fih-forks
Open

ci: fih: allow to configure container registry for fih docker image#2787
tpambor wants to merge 1 commit into
mcu-tools:mainfrom
tpambor:ci-fih-forks

Conversation

@tpambor

@tpambor tpambor commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

Currently, the container registry for the fih docker image is hardcoded to ghcr.io/mcu-tools. Forks of mcuboot can't run the fih tests workflow as-is, as the docker image is private to the mcu-tools organization. This commit allows to configure the container registry via the CONTAINER_REGISTRY environment variable and set it to ghcr.io/${{ github.repository_owner }} in the github workflow. Forks can then build and push the docker image to their own container registry and run the fih tests workflow.

Currently, the container registry for the fih docker image is
hardcoded to ghcr.io/mcu-tools. Forks of mcuboot can't run
the fih tests workflow as-is, as the docker image is private
to the mcu-tools organization. This commit allows to configure
the container registry via the CONTAINER_REGISTRY environment
variable and set it to 'ghcr.io/${{ github.repository_owner }}'
in the github workflow. Forks can then build and push the docker
image to their own container registry and run the fih tests
workflow.

Signed-off-by: Tim Pambor <tim.pambor@codewrights.de>
@tpambor
tpambor requested a review from d3zd3z as a code owner July 11, 2026 12:33
@tpambor

tpambor commented Jul 27, 2026

Copy link
Copy Markdown
Contributor Author

Anything missing to get this merged? @d3zd3z @nordicjm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants