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

Flag --incompatible_disable_target_provider_fields will break Envoy in Bazel 4.0 #9491

Closed
bazel-flag-bot opened this issue Dec 26, 2019 · 0 comments
Assignees
Labels
area/build no stalebot Disables stalebot from closing an issue

Comments

@bazel-flag-bot
Copy link

Incompatible flag --incompatible_disable_target_provider_fields will be enabled by default in Bazel 3.0, thus breaking Envoy.

The flag is documented here: bazelbuild/bazel#9014

Please check the following CI builds for build and test results:

Never heard of incompatible flags before? We have documentation that explains everything.

If you don't want to receive any future issues for Envoy or if you have any questions,
please file an issue in https://github.com/bazelbuild/continuous-integration

Important: Please do NOT modify the issue title since that might break our tools.

@mattklein123 mattklein123 added area/build no stalebot Disables stalebot from closing an issue labels Dec 26, 2019
@mattklein123 mattklein123 added this to the 1.14.0 milestone Dec 29, 2019
@mattklein123 mattklein123 modified the milestones: 1.14.0, 1.15.0 Mar 10, 2020
@lizan lizan changed the title Flag --incompatible_disable_target_provider_fields will break Envoy in Bazel 3.0 Flag --incompatible_disable_target_provider_fields will break Envoy in Bazel 4.0 Apr 21, 2020
@mattklein123 mattklein123 removed this from the 1.15.0 milestone Jun 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build no stalebot Disables stalebot from closing an issue
Projects
None yet
Development

No branches or pull requests

3 participants