Skip to content

ci: publish multi-arch images on every push to main - #787

Merged
bburda merged 2 commits into
mainfrom
ci/docker-multiarch-on-main
Nov 13, 2026
Merged

bburda merged 2 commits into
mainfrom
ci/docker-multiarch-on-main

Conversation

@mfaferek93

Copy link
Copy Markdown
Collaborator

Summary

docker-publish.yml built linux/amd64 only. arm64 targets (RevPi DiagBox, Jetson, RPi) got a fresh image only on a release tag, and the last release is 0.7.0 (2026-09-01). Anything merged since then never reached arm64 images.

This PR:

  • runs docker-publish-multiarch.yml on every push to main too, so :latest and sha-<short> are multi-arch (amd64 + arm64, each on a native runner, no QEMU)
  • keeps release tags as before (X.Y.Z, X.Y, sha-<short>, never :latest)
  • removes the amd64-only docker-publish.yml, so :latest has a single owner
  • adds a concurrency group: a newer push to main cancels an older build still running, tags are never cancelled
  • switches the build cache to mode=min (six scopes at mode=max would overrun the 10 GB Actions cache quota, the same reason the old workflow used mode=min)

The read-only OPC UA plugin inspection still runs on every arch before the merge job tags anything.

Testing

  • YAML parses. The trigger, tag and cache changes are small and follow the existing workflow.
  • First real proof is the run on merge: check that ghcr.io/selfpatch/ros2_medkit-jazzy:latest lists both amd64 and arm64 (docker manifest inspect).

Follow-up

The platform onboarding pins ros2_medkit-<distro>:0.7 because latest was amd64 only. After this lands, that pin can move to a newer multi-arch tag.

docker-publish.yml built amd64 only, so arm64 targets (RevPi, Jetson)
only got a fresh image at a release. The multi-arch workflow now also
runs on main: :latest and sha-<short> for amd64 and arm64 on native
runners. The amd64-only workflow is removed so :latest has one owner.
Copilot AI balanced review requested due to automatic review settings November 12, 2026 21:57

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.

@bburda bburda left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add the arch and tag scheme to the Pre-built Images section of docs/tutorials/docker.rst? Today it only says that images are published on every push to main. With this PR the gateway images are amd64 + arm64, with latest and sha-<short> from main, and X.Y.Z and X.Y from release tags. docs/tutorials/web-ui.rst already has a tag table like this for the web UI image.

A failed build job no longer skips the merge for every distro. The merge
refuses to tag unless both arch digests are present. The gha cache gave
almost no hits and evicted the ccache entries. Docs list the tag scheme.
@mfaferek93

Copy link
Copy Markdown
Collaborator Author

Could you add the arch and tag scheme to the Pre-built Images section of docs/tutorials/docker.rst?

Done in 7a07870. The section now says the images are amd64 + arm64 and has a tag table in the same format as web-ui.rst: latest + sha-<commit> from main, and X.Y.Z, X.Y, sha-<commit> from release tags.

@bburda
bburda merged commit 84332d0 into main Nov 13, 2026
25 checks passed
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.

3 participants