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
WIP - Update bazel prefix for 3.4.1 #98027
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
release-note-none
Denotes a PR that doesn't merit a release note.
kind/bug
Categorizes issue or PR as related to a bug.
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
size/XS
Denotes a PR that changes 0-9 lines, ignoring generated files.
do-not-merge/needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
area/apiserver
area/cloudprovider
area/code-generation
area/kubectl
area/kubelet
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
sig/auth
Categorizes an issue or PR as relevant to SIG Auth.
sig/cli
Categorizes an issue or PR as relevant to SIG CLI.
sig/cloud-provider
Categorizes an issue or PR as relevant to SIG Cloud Provider.
sig/cluster-lifecycle
Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
sig/instrumentation
Categorizes an issue or PR as relevant to SIG Instrumentation.
sig/network
Categorizes an issue or PR as relevant to SIG Network.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
and removed
do-not-merge/needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
labels
Jan 13, 2021
/priority important-soon |
k8s-ci-robot
added
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
labels
Jan 13, 2021
k8s-ci-robot
removed
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Jan 13, 2021
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
k8s-ci-robot
added
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
and removed
size/XS
Denotes a PR that changes 0-9 lines, ignoring generated files.
labels
Jan 13, 2021
k8s-ci-robot
added
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
and removed
size/S
Denotes a PR that changes 10-29 lines, ignoring generated files.
labels
Jan 13, 2021
k8s-ci-robot
added
the
area/dependency
Issues or PRs related to dependency changes
label
Jan 13, 2021
dims
reviewed
Jan 13, 2021
liggitt
changed the title
Update bazel prefix for 3.4.1
WIP - Update bazel prefix for 3.4.1
Jan 14, 2021
k8s-ci-robot
added
the
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
label
Jan 14, 2021
false alarm, had a bogus BUILD file import referencing an existing import by a different path |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/apiserver
area/cloudprovider
area/code-generation
area/dependency
Issues or PRs related to dependency changes
area/kubectl
area/kubelet
cncf-cla: yes
Indicates the PR's author has signed the CNCF CLA.
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
release-note-none
Denotes a PR that doesn't merit a release note.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
sig/auth
Categorizes an issue or PR as relevant to SIG Auth.
sig/cli
Categorizes an issue or PR as relevant to SIG CLI.
sig/cloud-provider
Categorizes an issue or PR as relevant to SIG Cloud Provider.
sig/cluster-lifecycle
Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
sig/instrumentation
Categorizes an issue or PR as relevant to SIG Instrumentation.
sig/network
Categorizes an issue or PR as relevant to SIG Network.
sig/node
Categorizes an issue or PR as relevant to SIG Node.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
size/M
Denotes a PR that changes 30-99 lines, ignoring generated files.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
What this PR does / why we need it:
The current value used for the importmap doesn't work with bazel 3.4.1 (updated in #96011).
running push-build with bazel 2.2.x:
with 3.4.1:
Requires kubernetes/kube-openapi#222 first
/cc @mikedanese