-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Allow staging via krel for kubetest #19328
Conversation
f86a335
to
8bf0091
Compare
548d181
to
33a9de4
Compare
a31c168
to
f833196
Compare
f833196
to
978d1c4
Compare
978d1c4
to
d2bf86b
Compare
d2bf86b
to
bf19bc0
Compare
This adds a new `--use-krel` flag to kubetest to indicate that we want to stage the sources directly via the API provided by k/release rather than the deprecated push-build.sh script (lives in k/release, too). The idea is to add another job later on for testing this flag on a non critical Kubernetes build+push job (should live in sig-release). Signed-off-by: Sascha Grunert <[email protected]>
bf19bc0
to
40ad443
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: saschagrunert The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@saschagrunert: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
return errors.Wrap( | ||
release.NewPushBuild(&release.PushBuildOptions{ | ||
Bucket: s.bucket, | ||
BuildDir: "_output", |
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.
TODO: We need a const for this somewhere, or a DefaultPushBuildOptions()
API.
I'll move these changes into kubetest2 and then we will continue there. |
This adds a new
--use-krel
flag to kubetest to indicate that we wantto stage the sources directly via the API provided by k/release rather
than the deprecated push-build.sh script (lives in k/release, too).
The idea is to add another job later on for testing this flag on a non
critical Kubernetes build+push job (should live in sig-release).
Refers to kubernetes/release#1578, kubernetes/release#1459