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

build: Support tags[] arg for more specific build control #8233

Merged
merged 2 commits into from
Sep 17, 2019
Merged

build: Support tags[] arg for more specific build control #8233

merged 2 commits into from
Sep 17, 2019

Conversation

achasveachas
Copy link
Contributor

Description:
Support tags[] arg for more specific build control.
Where the underlying bazel primitives support tags[], envoy_() should support them.

Risk Level: Low
Testing: Local on Windows and Linux CI
Docs Changes: None
Release Notes: None

Where the underlying bazel primitives support tags[], envoy_() should support them.

Signed-off-by: Yechiel Kalmenson <[email protected]>

Signed-off-by: William Rowe <[email protected]>
@junr03
Copy link
Member

junr03 commented Sep 13, 2019

@lizan do you mind taking a look at this?

@@ -90,6 +90,7 @@ def api_proto_library(
visibility = ["//visibility:private"],
srcs = [],
deps = [],
tags = [],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do you need tags even for api_proto_library? If you're not building the library/binary depends on them they're not built anyway.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You raise a good point, we introduced tags[] wherever we observed that the underlying bazel API's supported them, but this case may not be necessary for our purpose of excluding from Windows. It might be best to support them where they are valid, though?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do omit some parameter as "opinionated" wrapper of underlying bazel API and add tags/options for Envoy specific. I'm not feeling strongly on this so either way is fine.

@@ -90,6 +90,7 @@ def api_proto_library(
visibility = ["//visibility:private"],
srcs = [],
deps = [],
tags = [],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do omit some parameter as "opinionated" wrapper of underlying bazel API and add tags/options for Envoy specific. I'm not feeling strongly on this so either way is fine.

repository + "//test:main",
],
deps = select({
"@envoy//bazel:windows_x86_64": [repository + "//test:dummy_main"],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not needed at the end, and shouldn't included in this PR?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We saw this exclusion for Apple so we added it for Windows.

We don't have a strong opinion either way and we can remove this change.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@achasveachas the exclusion you mentioned is for fuzz I think? No platform should be excluded from normal cc_test.

Signed-off-by: William Rowe <[email protected]>
Signed-off-by: Yechiel Kalmenson <[email protected]>

Signed-off-by: William Rowe <[email protected]>
@repokitteh-read-only
Copy link

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to api/.

🐱

Caused by: #8233 was synchronize by achasveachas.

see: more, trace.

@lizan lizan added the api-review-required API review required by @envoyproxy/api-shepherds label Sep 17, 2019
Copy link
Member

@htuch htuch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@htuch htuch merged commit 0bce3a1 into envoyproxy:master Sep 17, 2019
danzh2010 pushed a commit to danzh2010/envoy that referenced this pull request Sep 24, 2019
…#8233)

Support tags[] arg for more specific build control.
Where the underlying bazel primitives support tags[], envoy_() should support them.

Risk Level: Low
Testing: Local on Windows and Linux CI

Signed-off-by: Yechiel Kalmenson <[email protected]>
danzh2010 pushed a commit to danzh2010/envoy that referenced this pull request Oct 4, 2019
…#8233)

Support tags[] arg for more specific build control.
Where the underlying bazel primitives support tags[], envoy_() should support them.

Risk Level: Low
Testing: Local on Windows and Linux CI

Signed-off-by: Yechiel Kalmenson <[email protected]>
danzh2010 pushed a commit to danzh2010/envoy that referenced this pull request Oct 4, 2019
…#8233)

Support tags[] arg for more specific build control.
Where the underlying bazel primitives support tags[], envoy_() should support them.

Risk Level: Low
Testing: Local on Windows and Linux CI

Signed-off-by: Yechiel Kalmenson <[email protected]>
@wrowe wrowe deleted the add-tags-arg branch November 5, 2019 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api-review-required API review required by @envoyproxy/api-shepherds
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants