| commit | 0d0caba2e940f9eec2051c43c86954cf9c95635f | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Thu Nov 16 22:09:18 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 16 22:10:14 2023 -0800 |
| tree | 7a1efae118244ca62322ae6bced00a3c9b83af0a | |
| parent | 3e3ae85fbb8dfac8cc7fb68e970f2f1bfa81ea9e [diff] |
Emit a fixed config segment with path stripping Instead of outright removing the config segment of exec paths with the stripping path mapper, replace it with a fixed string (`cfg`). This has the following benefits: * Actions that make assumptions about the general exec path structure (e.g. because they use the Bash runfiles library, which parses the exec path and expects a `bazel-out/<something>/bin/...` format) continue to work. * Path stripping becomes idempotent, which fixes issues in case an artifact's path is mapped both structurally and via the string-based stripping. Closes #20219. PiperOrigin-RevId: 583266215 Change-Id: I063fd7fd502a92660952427c5ce893eacd16436d
{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
