| commit | 946ded70aab712f986b6c8f683bb987b0eca230f | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <ci.bazel@gmail.com> | Fri Dec 06 20:54:59 2024 +0100 |
| committer | GitHub <noreply@github.com> | Fri Dec 06 19:54:59 2024 +0000 |
| tree | 3e11ed5ddcef48f727dd53c4569e2bc1e2d01411 | |
| parent | a31c5e108de1173d1cfb9cfa41991a9cfb706e50 [diff] |
[8.0.0] Only process executable path for path mapping (#24599) This fixes a few issues introduced in 282ac623df3523e2e31a2de9c002e5c50da19fec: * Only the executable path in the first argument of a `CommandLines` instance should be subject to path mapping. * String arguments that are not normalized as path strings and thus can't possibly be the optimized memory representation used for the executable arg by `StarlarkAction` should not be modified. Also removes an class that became unused in that commit. Closes #24576. PiperOrigin-RevId: 703536848 Change-Id: I358696bc268ab1f400798ef55ea4db8d556f07dd Commit https://github.com/bazelbuild/bazel/commit/b00576de25ad5eed2af6607f51ad004874079519 Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
{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
