Skip to content

fix(docker): switch to Buildx Bake matrix - #881

Merged
ReenigneArcher merged 1 commit into
masterfrom
fix/docker-workflow
Sep 4, 2026
Merged

fix(docker): switch to Buildx Bake matrix#881
ReenigneArcher merged 1 commit into
masterfrom
fix/docker-workflow

Conversation

@ReenigneArcher

Copy link
Copy Markdown
Member

Description

Refactors the reusable Docker workflow to use docker-bake.hcl as the single build source instead of scanning Dockerfiles and custom inline directives. It now resolves Bake targets/platforms into two matrices, runs one build per target+platform on native runner allowlists, and uses docker/bake-action with per-platform cache scopes and Bake set overrides.

Publishing is now digest-first: each platform build pushes by digest, uploads digest artifacts, and a new manifest job assembles final multi-platform tags for Docker Hub and GHCR (commit/test/latest/master/release tags). Artifact export is driven by an optional Bake artifacts group, and a new docker_complete gate ensures downstream release steps fail if build/manifest jobs fail or are cancelled.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

  • feat: New feature (non-breaking change which adds functionality)
  • fix: Bug fix (non-breaking change which fixes an issue)
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

  • Code follows the style guidelines of this project
  • Code has been self-reviewed
  • Code has been commented, particularly in hard-to-understand areas
  • Code docstring/documentation-blocks for new or existing methods/components have been added or updated
  • Unit tests have been added or updated for any new or modified functionality

AI Usage

See our AI usage policy.

  • None: No AI tools were used in creating this PR
  • Light: AI provided minor assistance (formatting, simple suggestions)
  • Moderate: AI helped with code generation or debugging specific parts
  • Heavy: AI generated most or all of the code changes

Comment thread .github/workflows/__call-docker.yml Fixed
Comment thread .github/workflows/__call-docker.yml Fixed
Comment thread .github/workflows/__call-docker.yml Fixed
@ReenigneArcher
ReenigneArcher force-pushed the fix/docker-workflow branch 2 times, most recently from eb3f101 to 3006936 Compare September 4, 2026 01:56
Refactors the reusable Docker workflow to use `docker-bake.hcl` as the single build source instead of scanning Dockerfiles and custom inline directives. It now resolves Bake targets/platforms into two matrices, runs one build per target+platform on native runner allowlists, and uses `docker/bake-action` with per-platform cache scopes and Bake `set` overrides.

Publishing is now digest-first: each platform build pushes by digest, uploads digest artifacts, and a new manifest job assembles final multi-platform tags for Docker Hub and GHCR (commit/test/latest/master/release tags). Artifact export is driven by an optional Bake `artifacts` group, and a new `docker_complete` gate ensures downstream release steps fail if build/manifest jobs fail or are cancelled.
@sonarqubecloud

sonarqubecloud Bot commented Sep 4, 2026

Copy link
Copy Markdown

@ReenigneArcher
ReenigneArcher marked this pull request as ready for review September 4, 2026 02:09
@ReenigneArcher
ReenigneArcher merged commit d6e0935 into master Sep 4, 2026
21 checks passed
@ReenigneArcher
ReenigneArcher deleted the fix/docker-workflow branch September 4, 2026 02:20
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