incompatible_skip_genfiles_symlink: Remove bazel-genfiles symlink #8651
Assignees
Labels
Comments
laurentlb
added
P1
|
@lberki, do you know how to do it? I'm not familiar with this code. |
|
It's in So it shouldn't be very hard, but I'm unable to sign up anyone on my team to following through with the incompatible flag process. Why is this a P1? |
|
My hope is that the change in Bazel is easy to do (we can reevaluate if it's not). Symlinks in the user directory are highly visible (anyone running Bazel will notice it). I'd rather remove it than have to document it. It's an incompatible change that will affect many people (https://github.com/search?q=bazel-genfiles&type=Code), so I'd rather do it earlier than later. |
|
This P1 bazel-1.0 issue is unassigned. Please assign cc @laurentlb |
laurentlb
changed the title
bazel-io
pushed a commit
that referenced
this issue
Jul 25, 2019
When set to true, the genfiles symlink is not created. #8651 RELNOTES: None. PiperOrigin-RevId: 259936511
bazel-io
pushed a commit
that referenced
this issue
Oct 10, 2019
Baseline: 97a8264 Cherry picks: + a0e3bb2: Remove support for authentication and .netrc + ada2c55: Add explicit --sdk argument to xcrun calls + 847df72: toolchain_vanilla: Unset source and target language level versions + 5cfa030: Update java_tools version to javac11-v5.1. Incompatible changes: - Python, Windows: the --[no]incompatible_windows_escape_python_args is no longer supported. (It was flipped to true in Bazel 0.27.0) - --incompatible_use_native_patch is enabled by default - Windows: --incompatible_windows_bashless_run_command is now true by default, meaning "bazel run //foo:bin" will run the binary as a subprocess of the Bazel client. (When the flag is false, the binary is executed as a subprocess of Bash.) - Windows: --incompatible_windows_native_test_wrapper is enabled by default New features: - Genrule now supports `cmd_bash`, `cmd_ps`, `cmd_bat` attributes. More details at https://docs.bazel.build/versions/master/be/general.html#genrule.c md - config_setting can now check multiple values on "--foo=firstVal --foo=secondVal ..."-style flags - tags: use `--experimental_allow_tags_propagation` flag to propagate tags to the action's execution requirements from targets. Such tags should start with: `no-`, `requires-`, `supports-`, `block-`, `disable-`, `cpu:`. See #8830 for details. - Users can now get generated def file from cc_library via "def_file" output group on Windows. - Platform-specific bazelrc: with --enable_platform_specific_config you can enable flags in bazelrc according to your host platform. - tags: use `--experimental_allow_tags_propagation` flag to propagate tags to the action's execution requirements from cc_library or cc_binary targets. Such tags should start with: `no-`, `requires-`, `supports-`, `block-`, `disable-`, `cpu:`. See #8830 for details. - tags: use --experimental_allow_tags_propagation flag to propagate tags to the action's execution requirements from java targets. Such tags should start with: no-, requires-, supports-, block-, disable-, cpu:. See #8830 for details. Important changes: - Bazel Android builds now use aapt2 by default. To revert to aapt, set `--android_aapt=aapt`. - Make either --subcommands or --verbose_failures imply --materialize_param_files - Bazel Android builds now use aapt2 by default. To revert to aapt, set `--an... RELNOTES: None - by default all remote connections considered to be via `gRPC` with TLS enabled, unless other specified. To disable TLS use `grpc://` prefix for you endpoints. All remote connections via `gRPC` affected - `--remote_cache`, `--remote_executor` or `--bes_backend`. http cache/executor is not affected. See #8061 for details. - cc_* rules support non-transitive defines through a 'local_defines' attribute. - Enable incompatible_disallow_rule_execution_platform_constraints_allowed by default (#8136). - incompatible_disallow_split_empty_separator is enabled by default - Fixed Android build issues with aapt2 on Windows. See the [GitHub issue](#9102) for more information. - --incompatible_disable_static_cc_toolchains has been flipped. See #8546. - --remote_default_platform_properties has been deprecated in favor of --remote_default_exec_properties. - The --incompatible_make_thinlto_command_lines_standalone flag has been flipped, see #6791 for more information. - The --incompatible_use_specific_tool_files flag has been flipped. See #9126 for more information. - Clarify default visibility. - Enables incompatible_auto_configure_host_platform - New incompatible flag --incompatible_disable_depset_items disables the "items" parameter in the Starlark depset constructor. Use "direct" and "transitive" parameters instead. - --incompatible_assignment_identifiers_have_local_scope is enabled - incompatible_disable_partition_default_parameter is enabled by default () - incompatible_restrict_attribute_names is enabled (#6437) - The --incompatible_disable_nocopts flag has been flipped. See #8546 for more information. - Deprecated Java-Starlark API java_common.create_provider is removed. JavaInfo() legacy args (actions, sources, source_jars, use_ijar, java_toolchain, host_javabase) are removed. - The flag incompatible_disallow_hashing_frozen_mutables is enabled (#7800) - `maven_jar` and `maven_server` now disallow using plain HTTP URLs without a specified checksum. If you are still using `maven_jar`, consider migrating to [`rules_jvm_external`](https://github.com/bazelbuild/rules_jvm_ext ernal) for transitive dependency management. See [#8607](#8607) for more information. - Added `sha256` and `sha256_src` attributes to `maven_jar`. Please consider migrating to SHA-256 as SHA-1 has been deemed cryptographically insecure ([https://shattered.io]()). Or, use [`rules_jvm_external`](https://github.com/bazelbuild/rules_jvm_ext ernal) to manage your transitive Maven dependencies with artifact pinning and SHA-256 verification support. - introducing per-target exec_properties - Bazel now supports ThinLTO builds on Linux for Clang versions >= 6.0. ThinLTO can be enabled through --features=thin_lto - The Target.output_group field in Starlark is removed. Use OutputGroupInfo instead. See #7949 for details. - Make a number of parameters of Starlark builtin functions positional-only (as opposed to specifiable by keyword). See #8147 for details. - incompatible_skip_genfiles_symlink is enabled by default (#8651) - Change Pruned events will fire immediately after being checked. - --incompatible_remove_legacy_whole_archive has been flipped. See #7362 for more information This release contains contributions from many people at Google, as well as Adam Liddell, Alessandro Patti, Arshabh Kumar Agarwal, Artem Pelenitsyn, Artem Zinnatullin, Benjamin Peterson, David Ostrovsky, Emmanuel Goh, Farhim Ferdous, George Gensure, iirina, Keith Smiley, Kiril Videlov, Laurent Le Brun, Mantas Sakalauskas, Marwan Tammam, Matt Mukerjee, panzhongxian, Shachar Anchelovich, Stepan Koltsov, Stephan Wolski, Travis Clarke, Yannic Bonenberger, Yuta Saito.
dslomov
pushed a commit
that referenced
this issue
Oct 11, 2019
Baseline: 97a8264 Cherry picks: + a0e3bb2: Remove support for authentication and .netrc + ada2c55: Add explicit --sdk argument to xcrun calls + 847df72: toolchain_vanilla: Unset source and target language level versions + 5cfa030: Update java_tools version to javac11-v5.1. Incompatible changes: - Python, Windows: the --[no]incompatible_windows_escape_python_args is no longer supported. (It was flipped to true in Bazel 0.27.0) - --incompatible_use_native_patch is enabled by default - Windows: --incompatible_windows_bashless_run_command is now true by default, meaning "bazel run //foo:bin" will run the binary as a subprocess of the Bazel client. (When the flag is false, the binary is executed as a subprocess of Bash.) - Windows: --incompatible_windows_native_test_wrapper is enabled by default New features: - Genrule now supports `cmd_bash`, `cmd_ps`, `cmd_bat` attributes. More details at https://docs.bazel.build/versions/master/be/general.html#genrule.c md - config_setting can now check multiple values on "--foo=firstVal --foo=secondVal ..."-style flags - tags: use `--experimental_allow_tags_propagation` flag to propagate tags to the action's execution requirements from targets. Such tags should start with: `no-`, `requires-`, `supports-`, `block-`, `disable-`, `cpu:`. See #8830 for details. - Users can now get generated def file from cc_library via "def_file" output group on Windows. - Platform-specific bazelrc: with --enable_platform_specific_config you can enable flags in bazelrc according to your host platform. - tags: use `--experimental_allow_tags_propagation` flag to propagate tags to the action's execution requirements from cc_library or cc_binary targets. Such tags should start with: `no-`, `requires-`, `supports-`, `block-`, `disable-`, `cpu:`. See #8830 for details. - tags: use --experimental_allow_tags_propagation flag to propagate tags to the action's execution requirements from java targets. Such tags should start with: no-, requires-, supports-, block-, disable-, cpu:. See #8830 for details. Important changes: - Bazel Android builds now use aapt2 by default. To revert to aapt, set `--android_aapt=aapt`. - Make either --subcommands or --verbose_failures imply --materialize_param_files - Bazel Android builds now use aapt2 by default. To revert to aapt, set `--an... RELNOTES: None - by default all remote connections considered to be via `gRPC` with TLS enabled, unless other specified. To disable TLS use `grpc://` prefix for you endpoints. All remote connections via `gRPC` affected - `--remote_cache`, `--remote_executor` or `--bes_backend`. http cache/executor is not affected. See #8061 for details. - cc_* rules support non-transitive defines through a 'local_defines' attribute. - Enable incompatible_disallow_rule_execution_platform_constraints_allowed by default (#8136). - incompatible_disallow_split_empty_separator is enabled by default - Fixed Android build issues with aapt2 on Windows. See the [GitHub issue](#9102) for more information. - --incompatible_disable_static_cc_toolchains has been flipped. See #8546. - --remote_default_platform_properties has been deprecated in favor of --remote_default_exec_properties. - The --incompatible_make_thinlto_command_lines_standalone flag has been flipped, see #6791 for more information. - The --incompatible_use_specific_tool_files flag has been flipped. See #9126 for more information. - Clarify default visibility. - Enables incompatible_auto_configure_host_platform - New incompatible flag --incompatible_disable_depset_items disables the "items" parameter in the Starlark depset constructor. Use "direct" and "transitive" parameters instead. - --incompatible_assignment_identifiers_have_local_scope is enabled - incompatible_disable_partition_default_parameter is enabled by default () - incompatible_restrict_attribute_names is enabled (#6437) - The --incompatible_disable_nocopts flag has been flipped. See #8546 for more information. - Deprecated Java-Starlark API java_common.create_provider is removed. JavaInfo() legacy args (actions, sources, source_jars, use_ijar, java_toolchain, host_javabase) are removed. - The flag incompatible_disallow_hashing_frozen_mutables is enabled (#7800) - `maven_jar` and `maven_server` now disallow using plain HTTP URLs without a specified checksum. If you are still using `maven_jar`, consider migrating to [`rules_jvm_external`](https://github.com/bazelbuild/rules_jvm_ext ernal) for transitive dependency management. See [#8607](#8607) for more information. - Added `sha256` and `sha256_src` attributes to `maven_jar`. Please consider migrating to SHA-256 as SHA-1 has been deemed cryptographically insecure ([https://shattered.io]()). Or, use [`rules_jvm_external`](https://github.com/bazelbuild/rules_jvm_ext ernal) to manage your transitive Maven dependencies with artifact pinning and SHA-256 verification support. - introducing per-target exec_properties - Bazel now supports ThinLTO builds on Linux for Clang versions >= 6.0. ThinLTO can be enabled through --features=thin_lto - The Target.output_group field in Starlark is removed. Use OutputGroupInfo instead. See #7949 for details. - Make a number of parameters of Starlark builtin functions positional-only (as opposed to specifiable by keyword). See #8147 for details. - incompatible_skip_genfiles_symlink is enabled by default (#8651) - Change Pruned events will fire immediately after being checked. - --incompatible_remove_legacy_whole_archive has been flipped. See #7362 for more information This release contains contributions from many people at Google, as well as Adam Liddell, Alessandro Patti, Arshabh Kumar Agarwal, Artem Pelenitsyn, Artem Zinnatullin, Benjamin Peterson, David Ostrovsky, Emmanuel Goh, Farhim Ferdous, George Gensure, iirina, Keith Smiley, Kiril Videlov, Laurent Le Brun, Mantas Sakalauskas, Marwan Tammam, Matt Mukerjee, panzhongxian, Shachar Anchelovich, Stepan Koltsov, Stephan Wolski, Travis Clarke, Yannic Bonenberger, Yuta Saito.
tensorflow-copybara
pushed a commit
to tensorflow/tensorflow
that referenced
this issue
Nov 6, 2019
Since Bazel 0.25, both bazel-genfiles and bazel-bin point to the same location. In Bazel 1.0, bazel-genfiles symlink won't be generated anymore, everything was there are now merged into bazel-bin folder. Related: bazelbuild/bazel#8651 PiperOrigin-RevId: 278815738 Change-Id: I0982662ad511e4fae1562a5cdd9c6543d7366480
MohamedNourArm
pushed a commit
to MohamedNourArm/tensorflow
that referenced
this issue
Nov 6, 2019
Since Bazel 0.25, both bazel-genfiles and bazel-bin point to the same location. In Bazel 1.0, bazel-genfiles symlink won't be generated anymore, everything was there are now merged into bazel-bin folder. Related: bazelbuild/bazel#8651 PiperOrigin-RevId: 278815738 Change-Id: I0982662ad511e4fae1562a5cdd9c6543d7366480
aherrmann-da
pushed a commit
to digital-asset/daml
that referenced
this issue
Nov 6, 2019
The bazel-genfiles symlink has been removed since Bazel 1.0. See bazelbuild/bazel#8651
aherrmann-da
pushed a commit
to digital-asset/daml
that referenced
this issue
Nov 6, 2019
The bazel-genfiles symlink has been removed since Bazel 1.0. See bazelbuild/bazel#8651
aherrmann-da
pushed a commit
to digital-asset/daml
that referenced
this issue
Nov 6, 2019
The bazel-genfiles symlink has been removed since Bazel 1.0. See bazelbuild/bazel#8651
aherrmann-da
pushed a commit
to digital-asset/daml
that referenced
this issue
Nov 7, 2019
The bazel-genfiles symlink has been removed since Bazel 1.0. See bazelbuild/bazel#8651
aherrmann-da
pushed a commit
to digital-asset/daml
that referenced
this issue
Nov 8, 2019
The bazel-genfiles symlink has been removed since Bazel 1.0. See bazelbuild/bazel#8651
aherrmann-da
added a commit
to digital-asset/daml
that referenced
this issue
Nov 11, 2019
* bazel: 0.28.1 --> 1.1.0 * bazel-watcher sha256 * Fix missing line in patch * proto_source_root --> strip_import_prefix See bazelbuild/bazel#7153 for details. * Update rules_nixpkgs Required to avoid errors of the form ``` ERROR: An error occurred during the fetch of repository 'node_nix': parameter 'sep' may not be specified by name, for call to method split(sep, maxsplit = None) of 'string' ``` and ``` ERROR: An error occurred during the fetch of repository 'node_nix': Traceback (most recent call last): File "/private/var/tmp/_bazel_runner/17d2b3954f1c6dcf5414d5453467df9a/external/io_tweag_rules_nixpkgs/nixpkgs/nixpkgs.bzl", line 149 _execute_or_fail(repository_ctx, <3 more arguments>) File "/private/var/tmp/_bazel_runner/17d2b3954f1c6dcf5414d5453467df9a/external/io_tweag_rules_nixpkgs/nixpkgs/nixpkgs.bzl", line 318, in _execute_or_fail fail(<1 more arguments>) Cannot build Nix attribute 'nodejs'. Command: [/Users/runner/.nix-profile/bin/nix-build, /private/var/tmp/_bazel_runner/17d2b3954f1c6dcf5414d5453467df9a/external/node_nix/nix/bazel.nix, "-A", "nodejs", "--out-link", "bazel-support/nix-out-link", "-I", "nixpkgs=/private/var/tmp/_bazel_runner/17d2b3954f1c6dcf5414d5453467df9a/external/nixpkgs/nixpkgs"] Return code: 1 Error output: src/main/tools/process-tools.cc:173: "setitimer": Invalid argument ``` * Update rules_scala * .proto has been removed, use [ProtoInfo] instead See https://docs.bazel.build/versions/1.1.0/be/protocol-buffer.html#proto_library * python3_nix add nix_file attribute To avoid the following error ``` ERROR: /home/aj/tweag.io/da/da-bazel-1.1/BUILD:66:1: //:nix_python3_runtime depends on @python3_nix//:bin/python in repository @python3_nix which failed to fetch. no such package '@python3_nix//': Traceback (most recent call last): File "/home/aj/.cache/bazel/_bazel_aj/5f825ad28f8e070f999ba37395e46ee5/external/io_tweag_rules_nixpkgs/nixpkgs/nixpkgs.bzl", line 149 _execute_or_fail(repository_ctx, <3 more arguments>) File "/home/aj/.cache/bazel/_bazel_aj/5f825ad28f8e070f999ba37395e46ee5/external/io_tweag_rules_nixpkgs/nixpkgs/nixpkgs.bzl", line 318, in _execute_or_fail fail(<1 more arguments>) Cannot build Nix attribute 'python3'. Command: [/home/aj/.nix-profile/bin/nix-build, "-E", "import <nixpkgs> { config = {}; overlays = []; }", "-A", "python3", "--out-link", "bazel-support/nix-out-link", "-I", "nixpkgs=/home/aj/.cache/bazel/_bazel_aj/5f825ad28f8e070f999ba37395e46ee5/external/nixpkgs/nixpkgs"] Return code: 1 Error output: error: anonymous function at /home/aj/.cache/bazel/_bazel_aj/5f825ad28f8e070f999ba37395e46ee5/external/nixpkgs/nixpkgs.nix:3:1 called with unexpected argument 'config', at (string):1:1 ``` * rules_haskell unnamed string.split(_, maxsplit = _) The keyword argument may no longer be named. * string.replace(_, _, maxsplit = _) may not be named * Move proto sources from deps to data Fixes ``` ERROR: /home/aj/tweag.io/da/da-bazel-1.1/daml-lf/archive/BUILD.bazel:150:1: in deps attribute of scala_test rule //daml-lf/archive:daml_lf_archive_reader_tests_test_suite_src_test_scala_com_digitalasset_daml_lf_archive_DecodeV1Spec.scala: '//daml-lf/archive:daml_lf_1.6_archive_proto_srcs' does not have mandatory providers: 'JavaInfo'. Since this rule was created by the macro 'da_scala_test_suite', the error might have been caused by the macro implementation ``` * Define sha256 for haskell_ghc__paths Bazel 1.1.0 fails on missing hashes. * Disable --incompatible_windows_native_test_wrapper * //compiler/daml-extension don't modify sources Modifying sources in-place can cause issues on Windows, where build actions are not sandboxed and changes on sources can affect other build steps. * bazel-genfiles --> bazel-bin The bazel-genfiles symlink has been removed since Bazel 1.0. See bazelbuild/bazel#8651 * Mark dev_env_tool repository rule as configure See https://docs.bazel.build/versions/1.1.0/skylark/lib/globals.html#repository_rule * Move data deps into data attribute * Mark dev_env_tool as local = True * Manually fetch @makensis_dev_env
bame-da
pushed a commit
to digital-asset/daml
that referenced
this issue
Nov 19, 2019
* bazel: 0.28.1 --> 1.1.0 * bazel-watcher sha256 * Fix missing line in patch * proto_source_root --> strip_import_prefix See bazelbuild/bazel#7153 for details. * Update rules_nixpkgs Required to avoid errors of the form ``` ERROR: An error occurred during the fetch of repository 'node_nix': parameter 'sep' may not be specified by name, for call to method split(sep, maxsplit = None) of 'string' ``` and ``` ERROR: An error occurred during the fetch of repository 'node_nix': Traceback (most recent call last): File "/private/var/tmp/_bazel_runner/17d2b3954f1c6dcf5414d5453467df9a/external/io_tweag_rules_nixpkgs/nixpkgs/nixpkgs.bzl", line 149 _execute_or_fail(repository_ctx, <3 more arguments>) File "/private/var/tmp/_bazel_runner/17d2b3954f1c6dcf5414d5453467df9a/external/io_tweag_rules_nixpkgs/nixpkgs/nixpkgs.bzl", line 318, in _execute_or_fail fail(<1 more arguments>) Cannot build Nix attribute 'nodejs'. Command: [/Users/runner/.nix-profile/bin/nix-build, /private/var/tmp/_bazel_runner/17d2b3954f1c6dcf5414d5453467df9a/external/node_nix/nix/bazel.nix, "-A", "nodejs", "--out-link", "bazel-support/nix-out-link", "-I", "nixpkgs=/private/var/tmp/_bazel_runner/17d2b3954f1c6dcf5414d5453467df9a/external/nixpkgs/nixpkgs"] Return code: 1 Error output: src/main/tools/process-tools.cc:173: "setitimer": Invalid argument ``` * Update rules_scala * .proto has been removed, use [ProtoInfo] instead See https://docs.bazel.build/versions/1.1.0/be/protocol-buffer.html#proto_library * python3_nix add nix_file attribute To avoid the following error ``` ERROR: /home/aj/tweag.io/da/da-bazel-1.1/BUILD:66:1: //:nix_python3_runtime depends on @python3_nix//:bin/python in repository @python3_nix which failed to fetch. no such package '@python3_nix//': Traceback (most recent call last): File "/home/aj/.cache/bazel/_bazel_aj/5f825ad28f8e070f999ba37395e46ee5/external/io_tweag_rules_nixpkgs/nixpkgs/nixpkgs.bzl", line 149 _execute_or_fail(repository_ctx, <3 more arguments>) File "/home/aj/.cache/bazel/_bazel_aj/5f825ad28f8e070f999ba37395e46ee5/external/io_tweag_rules_nixpkgs/nixpkgs/nixpkgs.bzl", line 318, in _execute_or_fail fail(<1 more arguments>) Cannot build Nix attribute 'python3'. Command: [/home/aj/.nix-profile/bin/nix-build, "-E", "import <nixpkgs> { config = {}; overlays = []; }", "-A", "python3", "--out-link", "bazel-support/nix-out-link", "-I", "nixpkgs=/home/aj/.cache/bazel/_bazel_aj/5f825ad28f8e070f999ba37395e46ee5/external/nixpkgs/nixpkgs"] Return code: 1 Error output: error: anonymous function at /home/aj/.cache/bazel/_bazel_aj/5f825ad28f8e070f999ba37395e46ee5/external/nixpkgs/nixpkgs.nix:3:1 called with unexpected argument 'config', at (string):1:1 ``` * rules_haskell unnamed string.split(_, maxsplit = _) The keyword argument may no longer be named. * string.replace(_, _, maxsplit = _) may not be named * Move proto sources from deps to data Fixes ``` ERROR: /home/aj/tweag.io/da/da-bazel-1.1/daml-lf/archive/BUILD.bazel:150:1: in deps attribute of scala_test rule //daml-lf/archive:daml_lf_archive_reader_tests_test_suite_src_test_scala_com_digitalasset_daml_lf_archive_DecodeV1Spec.scala: '//daml-lf/archive:daml_lf_1.6_archive_proto_srcs' does not have mandatory providers: 'JavaInfo'. Since this rule was created by the macro 'da_scala_test_suite', the error might have been caused by the macro implementation ``` * Define sha256 for haskell_ghc__paths Bazel 1.1.0 fails on missing hashes. * Disable --incompatible_windows_native_test_wrapper * //compiler/daml-extension don't modify sources Modifying sources in-place can cause issues on Windows, where build actions are not sandboxed and changes on sources can affect other build steps. * bazel-genfiles --> bazel-bin The bazel-genfiles symlink has been removed since Bazel 1.0. See bazelbuild/bazel#8651 * Mark dev_env_tool repository rule as configure See https://docs.bazel.build/versions/1.1.0/skylark/lib/globals.html#repository_rule * Move data deps into data attribute * Mark dev_env_tool as local = True * Manually fetch @makensis_dev_env
|
@laurentlb Should the docs be updated for this? https://docs.bazel.build/versions/master/output_directories.html#documentation-of-the-current-bazel-output-directory-layout |
mikedanese
added a commit
to mikedanese/test-infra
that referenced
this issue
Mar 24, 2020
bazel-bin and bazel-genfiles have pointed to the same location since 0.25. -genfiles is deprecated. This was test running: ../test-infra/scenarios/kubernetes_bazel.py --push With bazel version 2.2.0 and 0.23.2. Issue: bazelbuild/bazel#8651
mikedanese
added a commit
to mikedanese/test-infra
that referenced
this issue
Mar 24, 2020
bazel-bin and bazel-genfiles have pointed to the same location since 0.25. -genfiles is deprecated. This was test running: ../test-infra/scenarios/kubernetes_bazel.py --push With bazel version 2.2.0 and 0.23.2. Issue: bazelbuild/bazel#8651
mikedanese
added a commit
to mikedanese/release
that referenced
this issue
Mar 24, 2020
bazel-bin and bazel-genfiles have pointed to the same location since 0.25. -genfiles is deprecated. This was test running: ../release/push-build.sh --release-type=devel \ --bucket=kubernetes-release-mikedanese --private-bucket --nomock \ --version-suffix=mikedanese With bazel version 2.2.0 and 0.23.2. Issue: bazelbuild/bazel#8651
mikedanese
added a commit
to mikedanese/release
that referenced
this issue
Mar 24, 2020
bazel-bin and bazel-genfiles have pointed to the same location since 0.25. -genfiles is deprecated. This was test running: ../release/push-build.sh --release-type=devel \ --bucket=kubernetes-release-mikedanese --private-bucket --nomock \ --version-suffix=mikedanese With bazel version 2.2.0 and 0.23.2. Issue: bazelbuild/bazel#8651
justaugustus
added a commit
to justaugustus/release
that referenced
this issue
May 27, 2020
bazel-bin and bazel-genfiles have pointed to the same location since 0.25. -genfiles is deprecated. ref: bazelbuild/bazel#8651 Signed-off-by: Stephen Augustus <saugustus@vmware.com>
gitworkflows
pushed a commit
to khulnasoft-lab/gitiles
that referenced
this issue
May 15, 2024
Patch Set 1: > Patch Set 1: > > too late now, but next time, explain why. bazel-genfile does not exist any more, see: [1],[2]. * [1] https://groups.google.com/d/topic/bazel-dev/5iq7n1soenA/discussion * [2] bazelbuild/bazel#8651 Patch-set: 1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since Bazel 0.25 (and #6761), both
bazel-genfilesandbazel-binpoint to the same location.When the flag
incompatible_skip_genfiles_symlinkis set, thebazel-genfilessymlink is not created. This flag will be introduced in Bazel 0.29 and enabled by default in Bazel 1.0.This may break external scripts that refer to the
bazel-genfilessymlink. The fix is to replacebazel-genfileswithbazel-bin.The text was updated successfully, but these errors were encountered: