commit | 45d652ab279dee568ae94608b5db36121633e274 | [log] [tgz] |
---|---|---|
author | jmmv <jmmv@google.com> | Mon Mar 09 08:48:16 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 09 08:49:18 2020 -0700 |
tree | a7aef12abf58975eb365d684042b4edf65d621a3 | |
parent | 9108f6299c8ff3ab731052dfbee245fa4981988b [diff] |
Ensure the workspace name appears in paths within sandboxfs sandboxes. Some tools walk path hiearchies looking for the workspace name and misbehave if that component is not present. All sandboxed spawn runners have provisions to deal with this and explicitly add the workspace name to the execroots they generate... but the sandboxfs spawn runner was not doing so. Fix it now. RELNOTES: None. PiperOrigin-RevId: 299850812
{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