| commit | b76cc3a2ec4991bb5772ce309fae288e147bcebe | [log] [tgz] |
|---|---|---|
| author | Jonathan Gerrish <jonathan@indiekid.org> | Thu Jul 28 13:30:49 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 28 13:32:12 2022 -0700 |
| tree | 6f03a96c292d03c838bc957161fcc2deafa5e9c0 | |
| parent | bc20798813f69bb27c3cf8192d69e6db117639c4 [diff] |
Reduce AndroidAssetMerger intermediate outputs They are not required in the final build. For our builds:- This results in 503MB of outputs (assets.zip files) - each of these includes the transitive closure of all assets. To put in perspective we have only 2.5MB of assets. This is very costly for remote builds with caches especially on slower connections If resource conflict checking is not enabled (it is not for our build) this will also avoid running AndroidAssetMerger all together saving 896 actions ~3mins total CPU time. https://github.com/bazelbuild/rules_android/issues/10 Closes #11303. PiperOrigin-RevId: 463912957 Change-Id: I61b0cdd03ce5bdfd70f17feaf03529a683cddefc
{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
