-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Docker build/push should not use a matrix #2544
🐛 Docker build/push should not use a matrix #2544
Conversation
/assign @ncdc |
.github/workflows/kcp-image.yaml
Outdated
@@ -60,14 +54,14 @@ jobs: | |||
type=raw,value=${{ env.sha_short }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not in the direct scope, but maybe an opportunity to have that replaced with type=sha,prefix=,suffix=,format=short
so the logic that computes / sets sha_short
can be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done ptal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
By using a matrix github actions spins up different VMs to build these images, upon pushing tags and the manifest, the different VMs have no information about the other builds, so each build context will build and push a manifest only for its own image. Signed-off-by: Vince Prignano <[email protected]>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ncdc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
By using a matrix github actions spins up different VMs to build these images, upon pushing tags and the manifest, the different VMs have no information about the other builds, so each build context will build and push a manifest only for its own image.
Signed-off-by: Vince Prignano [email protected]
Summary
Related issue(s)
Fixes #