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

fix bazel calls when using local envoy and --override_repository #2578

Merged
merged 1 commit into from
Nov 22, 2019

Conversation

clarketm
Copy link
Member

@clarketm clarketm commented Nov 21, 2019

What this PR does / why we need it:
For performing build/test operations with a local envoy source; one configured via the --override_repository flag.

Otherwise, bazel will emit errors like:

ERROR: An error occurred during the fetch of repository 'envoy'

and

ERROR: no such package @envoy//...

on bazel info calls (since the override flag is unknown to the command) which is problematic for some/most make targets that need to be aware of the envoy binary or bazel output locations.

cc @howardjohn @yxue

@istio-testing istio-testing added the do-not-merge/work-in-progress Block merging of a PR because it isn't ready yet. label Nov 21, 2019
@googlebot googlebot added the cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. label Nov 21, 2019
@istio-testing istio-testing added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Nov 21, 2019
@clarketm clarketm changed the title fix bazel with --override_repository fix bazel calls when using local envoy and --override_repository Nov 21, 2019
@clarketm
Copy link
Member Author

clarketm commented Nov 21, 2019

The presubmit test failures are related to a change in an upstream dependency: envoyproxy/envoy#9072 that needs to be pulled/cherrypicked in.

@istio-testing istio-testing 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 Nov 21, 2019
@clarketm clarketm force-pushed the fix-bazel-info branch 2 times, most recently from 518f0fc to b2f230e Compare November 21, 2019 08:03
@clarketm clarketm marked this pull request as ready for review November 21, 2019 18:43
@clarketm clarketm requested a review from a team November 21, 2019 18:43
@istio-testing istio-testing removed the do-not-merge/work-in-progress Block merging of a PR because it isn't ready yet. label Nov 21, 2019
@clarketm clarketm added the cherrypick/release-1.4 Set this label on a PR to auto-merge it to the release-1.4 branch label Nov 21, 2019
@istio-testing
Copy link
Collaborator

In response to a cherrypick label: new pull request created: #2580

@clarketm clarketm deleted the fix-bazel-info branch November 23, 2019 07:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherrypick/release-1.4 Set this label on a PR to auto-merge it to the release-1.4 branch cla: yes Set by the Google CLA bot to indicate the author of a PR has signed the Google CLA. 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.

7 participants