commit | 5072f6f2eb5e76ccb39e1e1b9298d5d519fb1434 | [log] [tgz] |
---|---|---|
author | aiuto <aiuto@google.com> | Mon Aug 17 21:01:33 2020 -0700 |
committer | Tony Aiuto <aiuto@google.com> | Wed Sep 02 16:07:17 2020 -0400 |
tree | 40347d1e8a9ac186e44060a6ee1a40ee23c0e80a | |
parent | 8baa20bd17c82ddf25a8d59040af8b14b82d4d53 [diff] |
Stop needlessly parsing WORKSPACE files from external repositories. Fixes: https://github.com/bazelbuild/bazel/issues/11936 I have an additional test to prove the spurious error message is gone and that I still can refer to a workspace by name, in https://github.com/aiuto/repro_11936/tree/more_tests I have not added it yet because it is not really clear what the correct behavior should be for external repos - should the WORKSPACE be valid and used, or ignored. This change brings the code in line with the documentation (ignored), but the better behavior might be different. RELNOTES: Stop needlessly parsing WORKSPACE files from external repositories. PiperOrigin-RevId: 327157715
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md