| commit | f788fedbcf0d69568f7cdf17326d594a861da797 | [log] [tgz] |
|---|---|---|
| author | Ian (Hee) Cha <heec@google.com> | Wed Feb 21 12:06:45 2024 -0800 |
| committer | GitHub <noreply@github.com> | Wed Feb 21 20:06:45 2024 +0000 |
| tree | ef54a670c7643801ac1aaf9b4b11b1f9150c779e | |
| parent | 22948f3fd643275795262664e2eb1e32e5ec8a42 [diff] |
[7.1.0] Use execution info instead of hard-coded mnemonics for Java path mapping (#21461) By removing Java rules from the hard-coded mnemonics allowlist for path mapping, users can rely on `--modify_execution_info` to selectively disable path mapping for them just like for Starlark actions. This requires fixing two minor inconsistencies in how execution info is populated for Java actions: * In `JavaCompilationHelper`, `buildKeepingLast` is used instead of `buildOrThrow` to prevent a crash when a target sets `supports-path-mapping` via `tags`. * In `JavaHeaderCompileAction`, `--experimental_inmemory_jdeps_files` no longer causes all other execution info to be lost. Fixes #21092 Closes #21093. Commit https://github.com/bazelbuild/bazel/commit/f8337c754c8c1b27b34b84cde2c608c802266e96 PiperOrigin-RevId: 609064092 Change-Id: I6803e34a6861f19d185542e707b00029ee018a0a 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
