Google Git
Sign in
bazel / bazel / 9108f6299c8ff3ab731052dfbee245fa4981988b
commit9108f6299c8ff3ab731052dfbee245fa4981988b[log] [tgz]
authorjmmv <jmmv@google.com>Mon Mar 09 08:27:32 2020 -0700
committerCopybara-Service <copybara-worker@google.com>Mon Mar 09 08:28:43 2020 -0700
treeb1a2ce7da9fd2df7c908ffd9b41540421af78e8c
parentd30061591beeb91a68cc47bd3f1fe735724986a6 [diff]
Add sandboxfs support to the processwrapper-sandbox spawn runner.

The lack of this is an overlook from when I first added sandboxfs support
to the linux-sandbox and darwin-sandbox spawn runners.  I noticed this
by chance when doing some sandboxfs work on a Debian VM, where namespaces
are not allowed for unprivileged users.  I saw that my builds were using
the processwrapper-sandbox, not the linux-sandbox, and that they were not
using sandboxfs.

I know that this comes with no tests.  There currently are not tests to
validate a real build with sandboxfs enabled.  If there were, these tests
should verify the behavior with the platform-specific spawn runner and
now also with the more generic processwrapper-sandbox.  However, adding
these tests is pretty complicated and their benefit would be pretty low
at this point (because sandboxfs is not present in Bazel CI so we would
not run them automatically).  I'll work on these later if we decide to
make further progress on this feature.

RELNOTES: None.
PiperOrigin-RevId: 299846783
2 files changed
tree: b1a2ce7da9fd2df7c908ffd9b41540421af78e8c
  1. .bazelci/
  2. examples/
  3. scripts/
  4. site/
  5. src/
  6. third_party/
  7. tools/
  8. .bazelrc
  9. .gitattributes
  10. .gitignore
  11. AUTHORS
  12. BUILD
  13. CHANGELOG.md
  14. CODEOWNERS
  15. combine_distfiles.py
  16. combine_distfiles_to_tar.sh
  17. compile.sh
  18. CONTRIBUTING.md
  19. CONTRIBUTORS
  20. distdir.bzl
  21. ISSUE_TEMPLATE.md
  22. LICENSE
  23. README.md
  24. WORKSPACE
README.md

Bazel

{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.

Getting Started

Documentation

Contributing to Bazel

See CONTRIBUTING.md

Build status