| commit | 3e2329a73ffd5d60e5e2babe60ebe5bf322c07da | [log] [tgz] |
|---|---|---|
| author | Philipp Wollermann <philwo@google.com> | Fri Mar 24 09:47:11 2017 +0000 |
| committer | Yue Gan <yueg@google.com> | Fri Mar 24 12:20:06 2017 +0000 |
| tree | b1a66c81c4e59eedc84fb28bc8a02ec68fe3ed73 | |
| parent | 2879971666e0cc3f1f24ae91b88c4400af77e7f3 [diff] |
sandbox: Remove the flag --sandbox_block_path. It is in the way of optimizing the performance of the sandbox, because it requires us to create two helper files (an unreadable file and an unreadable directory) which are bind-mounted on top of paths specified via this flag. These two helper files were created on a tmpfs mounted by the sandbox until now, which ensured that they were automatically deleted on exit. However, mounting tmpfs on /dev/shm or /tmp causes issues like #2686 or #1882. By removing this flag, we can get rid of the two helper files, which means we can also remove the reliance on a "sandbox temp directory" completely in the next change. -- PiperOrigin-RevId: 151107496 MOS_MIGRATED_REVID=151107496
- src/main/java/com/google/devtools/build/lib/sandbox/DarwinSandboxRunner.java[diff]
- src/main/java/com/google/devtools/build/lib/sandbox/DarwinSandboxedStrategy.java[diff]
- src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxRunner.java[diff]
- src/main/java/com/google/devtools/build/lib/sandbox/LinuxSandboxedStrategy.java[diff]
- src/main/java/com/google/devtools/build/lib/sandbox/SandboxOptions.java[diff]
- src/main/java/com/google/devtools/build/lib/sandbox/SandboxStrategy.java[diff]
- src/main/tools/linux-sandbox-options.cc[diff]
- src/main/tools/linux-sandbox-options.h[diff]
- src/main/tools/linux-sandbox-pid1.cc[diff]
- src/main/tools/linux-sandbox.cc[diff]
- src/test/shell/bazel/bazel_sandboxing_test.sh[diff]
- examples/
- scripts/
- site/
- src/
- third_party/
- tools/
- .gitattributes
- .gitignore
- AUTHORS
- BUILD
- CHANGELOG.md
- combine_distfiles.sh
- compile.sh
- CONTRIBUTING.md
- CONTRIBUTORS
- ISSUE_TEMPLATE.md
- LICENSE
- LICENSE.txt
- README.md
- WORKSPACE
Bazel (Beta)
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google's software, and thus it has been designed to handle build problems present in Google's development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.
Getting Started
- How to install Bazel
- How to get started using Bazel
- The Bazel command line is documented in the user manual
- The rule reference documentation is in the build encyclopedia
- How to use the query command
- How to extend Bazel
- The test environment is described on the page writing tests
About the Bazel project
- How to contribute to Bazel
- Our governance plan
- Future plans are in the roadmap
- For each feature, which level of support to expect
- Current Bazel Release Candidate