-
Notifications
You must be signed in to change notification settings - Fork 505
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
look for version in bazel-bin #1211
Conversation
@mikedanese: 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. |
bazel-bin and bazel-genfiles have pointed to the same location since 0.25. -genfiles is deprecated. This was test running: ../release/push-build.sh --release-type=devel \ --bucket=kubernetes-release-mikedanese --private-bucket --nomock \ --version-suffix=mikedanese With bazel version 2.2.0 and 0.23.2. Issue: bazelbuild/bazel#8651
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
/approve
/hold
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fejta, justaugustus, mikedanese 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 |
bazel-bin and bazel-genfiles have pointed to the same location since
0.25. -genfiles is deprecated.
This was test running:
With bazel version 2.2.0 and 0.23.2. Not sure how to test ./pkg/release but we have unit tests there.
Issue: bazelbuild/bazel#8651
/assign @justaugustus @fejta