-
Notifications
You must be signed in to change notification settings - Fork 303
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
Build binaries for docker images in cloudbuild.yaml #2108
Conversation
/ok-to-test |
/assign @aojea |
cloudbuild.yaml
Outdated
args: | ||
- -c | ||
- | | ||
echo "build binaries" |
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.
what about using two different steps, one for each command?
https://cloud.google.com/build/docs/build-config-file-schema#yaml_8
/hold I don't have the same problem
|
/hold cancel |
3217890
to
8de0d7a
Compare
The actual problem is that binaries that are built are not multiarch but amd in multiarch wrapping https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/post-ingress-gce-push-image/1656111566392659968#1:build-log.txt%3A1360 @aojea PTAL |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, code-elinka 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 |
args: | ||
- -c | ||
- | | ||
VERBOSE="${VERBOSE}" make all-build |
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.
is this failing now?
you don't need to add it here since is already in the env
If I run an image: gcr.io/k8s-ingress-image-push/ingress-gce-e2e-test
I see an error:
It means it doesn't have binaries that were supposed to be copied.
This change adds a line that builds those binaries (make all-build).