This repository has been archived by the owner on Jan 26, 2022. It is now read-only.
Bazel incompatible flags #50
Assignees
Comments
greggdonovan
added a commit
to greggdonovan/BUILD_file_generator
that referenced
this issue
Mar 12, 2019
…vider --incompatible_depset_union. Other failing checks depend on upstream updates of rules_scala and protobuf.
greggdonovan
added a commit
to greggdonovan/BUILD_file_generator
that referenced
this issue
Mar 12, 2019
…vider --incompatible_depset_union. Other failing checks depend on upstream updates of rules_scala and protobuf.
petroseskinder
pushed a commit
that referenced
this issue
Mar 13, 2019
…compatible_depset_union. (#51) Other failing checks depend on upstream updates of rules_scala and protobuf.
petroseskinder
assigned petroseskinder and greggdonovan and unassigned greggdonovan and petroseskinder
|
thanks for updating @greggdonovan |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From our latest CI run (https://buildkite.com/bazel/bazelisk-plus-incompatible-flags/builds/28#d18600f5-284d-41fa-ae37-b0e51d2e2ff8), migration is needed for the following flags:
* --incompatible_depset_is_not_iterable
* --incompatible_depset_union
* --incompatible_disable_deprecated_attr_params
* --incompatible_disable_legacy_proto_provider
* --incompatible_use_toolchain_providers_in_java_common
In particular, depsets flags have been around for a while.
Documentation is here: https://docs.bazel.build/versions/master/skylark/depsets.html
Let me know if you need help
The text was updated successfully, but these errors were encountered: