| commit | d3435b09d89f25bf5008ef3b9c870c835d51a8da | [log] [tgz] |
|---|---|---|
| author | pcloudy <pcloudy@google.com> | Tue Apr 12 08:42:43 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 12 08:43:55 2022 -0700 |
| tree | aca3edf44b1fb023da81db91e3a3bb635338cb81 | |
| parent | 5c73d86f989b7cd31a68f452a078b725e610bb58 [diff] |
Seperate GetSelfPath implementation for Blaze and Bazel In Blaze, we keep using "/proc/self/exe", but in Bazel we resolve this symlink to the actual Bazel binary. This is essentially a rollback of https://github.com/bazelbuild/bazel/commit/d79ec039a42feea4e4c059eca29f64b40aa8583a only for Bazel, because it solved an issue that rare in Bazel, but it's preventing users from running Bazel inside a Linux docker container on Apple Silicon machines. Fixes https://github.com/bazelbuild/bazel/issues/15076 Closes https://github.com/bazelbuild/bazel/pull/14391 RELNOTES: None PiperOrigin-RevId: 441198110
{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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
