| commit | 1154a3f779256e3b45eb33b22693697f2000c815 | [log] [tgz] |
|---|---|---|
| author | Alex Humesky <ahumesky@google.com> | Tue Feb 28 15:42:07 2023 -0500 |
| committer | GitHub <noreply@github.com> | Tue Feb 28 12:42:07 2023 -0800 |
| tree | 25072e43ba1f01e7e634b28905a44ddc7fe83c63 | |
| parent | d4105e658001677929338835eb970e6595e66b3c [diff] |
make desugar dependencies deterministic (#17217) Desugar dependencies are added to the result jar file as metadata, this desugar dependency object contains a few lists that we found out the order of this list can be different in different builds with the same inputs, therefore the final result will have a different hash and it cause cache miss in the builds solution is to make the lists in this object sorted. So for the same input, we always get the same output Closes #16859. PiperOrigin-RevId: 500842557 Change-Id: I051e74e7147d590fcfe5cda9731b8e012396bb65 Co-authored-by: mohamadk <mohamad.khaleghy@gmail.com> Co-authored-by: kshyanashree <109167932+kshyanashree@users.noreply.github.com>
{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
