| commit | f5d76b1777ce861a7e551342fe25363517d53ff5 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri Feb 09 11:26:27 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Feb 09 11:27:57 2024 -0800 |
| tree | 05ad1a4fe56b65498e9858a160dab8f42c207a99 | |
| parent | 5ff7c61842c6a3418e516a3dec53dd924ea65edf [diff] |
Automated rollback of commit fd196bf03f4301cc3fbfc307570637f4de71c82c. *** Reason for rollback *** Huge memory regression [] *** Original change description *** Also path map transitive header jar paths with direct classpath optimization `JavaHeaderCompileAction` can apply an optimization where it compiles the source files only against direct dependencies, making use of the fact that Turbine includes sufficient information about transitive dependencies into the direct header jars in a special directory. In order to ensure that downstream consumers of header compilation action can use its `.jdeps... *** PiperOrigin-RevId: 605686218 Change-Id: Id8f9cff98659af94a57c87025cb8e23c8acf1d67
{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
