Skip to content
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

Closed

Conversation

saschagrunert
Copy link
Member

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).

Refers to kubernetes/release#1578, kubernetes/release#1459

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Sep 23, 2020
@k8s-ci-robot k8s-ci-robot added area/kubetest sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Sep 23, 2020
go.mod Outdated Show resolved Hide resolved
kubetest/stage.go Outdated Show resolved Hide resolved
@saschagrunert saschagrunert force-pushed the stage-via-krel branch 2 times, most recently from f86a335 to 8bf0091 Compare September 23, 2020 20:15
@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Sep 23, 2020
@saschagrunert saschagrunert force-pushed the stage-via-krel branch 7 times, most recently from 548d181 to 33a9de4 Compare September 24, 2020 08:45
@k8s-ci-robot k8s-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Sep 24, 2020
@saschagrunert saschagrunert force-pushed the stage-via-krel branch 3 times, most recently from a31c168 to f833196 Compare September 24, 2020 12:21
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Sep 24, 2020
@k8s-ci-robot k8s-ci-robot removed the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 24, 2020
@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Sep 24, 2020
@k8s-ci-robot k8s-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Sep 24, 2020
@k8s-ci-robot k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Sep 24, 2020
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]>
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Sep 24, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: saschagrunert
To complete the pull request process, please assign amwat
You can assign the PR to them by writing /assign @amwat in a comment when ready.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot
Copy link
Contributor

@saschagrunert: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-test-infra-bazel 40ad443 link /test pull-test-infra-bazel

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",
Copy link
Member Author

@saschagrunert saschagrunert Sep 24, 2020

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.

@saschagrunert
Copy link
Member Author

I'll move these changes into kubetest2 and then we will continue there.

@saschagrunert saschagrunert deleted the stage-via-krel branch September 24, 2020 21:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubetest cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants