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

Update for bazel incompatible changes #198

Merged
merged 1 commit into from
May 22, 2019
Merged

Update for bazel incompatible changes #198

merged 1 commit into from
May 22, 2019

Conversation

keith
Copy link
Contributor

@keith keith commented May 17, 2019

When building envoy with bazel@HEAD to test for regressions, bazel CI
tests with upcoming incompatible changes. This PR fixes a few of those
experienced upstream:

--incompatible_require_ctx_in_configure_features & --incompatible_enable_cc_toolchain_resolution:

Updated rules_go to include upstream fixes for these.

--incompatible_depset_is_not_iterable:

Call to_list where needed

--incompatible_disable_deprecated_attr_params:

Change single_file to allow_single_file

--incompatible_no_support_tools_in_action_inputs:

Move ctx.executable._plugin to tools instead of inputs

--incompatible_disable_legacy_proto_provider:

Update proto API usage following bazelbuild/bazel#7152

@keith
Copy link
Contributor Author

keith commented May 17, 2019

So this build fails without my changes too, I'll investigate #199

@keith
Copy link
Contributor Author

keith commented May 17, 2019

Ok I will rebase this after #200 is merged which seemed to fix the issue

@htuch
Copy link
Contributor

htuch commented May 21, 2019

@keith I just merged #200

When building envoy with bazel@HEAD to test for regressions, bazel CI
tests with upcoming incompatible changes. This PR fixes a few of those
experienced upstream:

`--incompatible_require_ctx_in_configure_features` & `--incompatible_enable_cc_toolchain_resolution`:

Updated rules_go to include upstream fixes for these.

`--incompatible_depset_is_not_iterable`:

Call `to_list` where needed

`--incompatible_disable_deprecated_attr_params`:

Change `single_file` to `allow_single_file`

`--incompatible_no_support_tools_in_action_inputs`:

Move `ctx.executable._plugin` to `tools` instead of `inputs`

`--incompatible_disable_legacy_proto_provider`:

Update proto API usage following bazelbuild/bazel#7152

Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
@keith
Copy link
Contributor Author

keith commented May 21, 2019

Updated removing the gazelle commit (is that ok?) and we're green! Thanks @htuch!

@keith
Copy link
Contributor Author

keith commented May 22, 2019

Also I'm not sure what the release process is with this repo, but if possible it would be great to create a new release once this is merged so we can fix envoyproxy/envoy#6995 upstream!

Copy link
Contributor

@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! @rodaine can you cut a release? I can do it too, but LMK if there is any magic I should do at the same time.

@htuch htuch merged commit 26db5cb into bufbuild:master May 22, 2019
@keith keith deleted the ks/incompatible-changes branch May 22, 2019 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants