-
Notifications
You must be signed in to change notification settings - Fork 507
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
push-build: Support pushing cross builds to a /cross subdirectory #1386
Conversation
build_type is used as an option but not plumbed to any logic in release::gcs::locally_stage_release_artifacts, so we remove it here. Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
@justaugustus: Adding label: Reasons for blocking this PR:[Changes to certain release tools can affect our ability to test, build, and release Kubernetes. This PR must be explicitly approved by SIG Release repo admins.] Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hasheddan, justaugustus 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 |
What type of PR is this?
/kind feature cleanup
/priority critical-urgent
What this PR does / why we need it:
Follow-up to #1385.
/assign @tpepper @hasheddan @saschagrunert @cpanato
cc: @kubernetes/release-engineering @BenTheElder @spiffxp
ref: kubernetes/sig-release#850, kubernetes/sig-release#759
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
I'll come back with more details shortly; just getting the PR up in the meantime.
Does this PR introduce a user-facing change?