ci: enable arm64 in build matrix (linux/amd64,linux/arm64)#27
Merged
ycpss91255 merged 2 commits intomainfrom Apr 24, 2026
Merged
ci: enable arm64 in build matrix (linux/amd64,linux/arm64)#27ycpss91255 merged 2 commits intomainfrom
ycpss91255 merged 2 commits intomainfrom
Conversation
PR #23 rebuilt devel from a multi-arch base for Jetson support, but main.yaml never opted in to the template's arm64 build matrix — the build-worker.yaml input defaults to linux/amd64 only. As a result, every PR since #23 has only verified amd64 in CI; arm64 has been validated manually via rsync-to-Jetson. Pass platforms: linux/amd64,linux/arm64 to build-worker.yaml so CI runs both architectures in parallel (template v0.9.11 added the ubuntu-24.04-arm runner support).
This was referenced Apr 24, 2026
v0.9.13's release-test-tools.yaml shipped a multi-arch ghcr.io/ycpss91255-docker/test-tools:v0.9.13 with x86_64 shellcheck / hadolint binaries in BOTH manifest variants — the `ARG TARGETARCH=amd64` default in template/dockerfile/Dockerfile.test-tools shadowed BuildKit's per-platform auto-inject (moby/buildkit#3403), so every multi-arch run fell back to amd64. This branch enabled the arm64 matrix but kept pointing at @v0.9.13, so the arm64 shard blew up at `shellcheck: Exec format error` on first run. Template v0.10.0-rc2 (#126 / #127) drops the ARG default. The rc2 GHCR image's arm64 variant contains real aarch64 binaries (verified via `docker cp` + `file`). Bumping build-worker.yaml + release- worker.yaml @tag so this PR's arm64 shard picks up the correct image.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
develfrom a multi-arch base (ros:foxy-ros-base-focal) so Jetson (arm64) is supported, but.github/workflows/main.yamlnever opted in to the template's arm64 build matrix —build-worker.yaml'splatformsinput defaults tolinux/amd64only.rsyncto the Jetson.platforms: linux/amd64,linux/arm64tobuild-worker.yamlso CI runs both architectures in parallel. The template'subuntu-24.04-armrunner support has been in place since v0.9.11.Test plan
compute-matrixemits two entries: amd64 + arm64build (linux/amd64, ...)passesbuild (linux/arm64, ubuntu-24.04-arm, aarch64)passes (this is the new check we're verifying)