ci: switch to use cloud builders for native multi-arch support #7
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.
Initial test using the docker cloud builder for building and pushing multi-arch images.
This PR completely replaces the shared CI workflow with one that is set up to leverage Docker Cloud Builders. Secrets have been pushed to leverage the builder within its configuration. Fundamentally not much has changed other than 'where' the work is being done. Things to consider:
push to main
andtag
docker buildx bake
for local builds leveraging local architectureNOTE: If builds fail please notify me, we may have run through our allocated minutes
NOTE: There is an option that we could run local AMD builds on GH directly for testing, and only build both arch for prod use, but for now to keep things simply we are leveraging the cloud builder for all and its cache system.