commit | 39ac64a8b9b939dd179b5b69ceee3b007e225ee9 | [log] [tgz] |
---|---|---|
author | Kerrick Staley <kstaley@lyft.com> | Mon Jul 20 22:58:52 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Jul 20 22:59:46 2020 -0700 |
tree | 6763614f32dcca2d4a424d5e08e5b3a9119c191b | |
parent | cf3a9236f8af53a61c4b89546611029f35779481 [diff] |
try-import user.bazelrc from the root of the repo Using the syntax `try-import user.bazelrc` will try to import the file from the CWD, so as you move around in your repo your Bazel settings will change. Using the syntax `try-import %workspace%/user.bazelrc` will always import the file `user.bazelrc` from the root of the repo, which fixes this problem. Related to https://github.com/bazelbuild/bazel/issues/11803 Closes #11804. PiperOrigin-RevId: 322298509
{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