| commit | acc1e0f747f14d1cac571890f97fa6c494344797 | [log] [tgz] |
|---|---|---|
| author | adonovan <adonovan@google.com> | Tue Jan 12 06:53:46 2021 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 12 06:54:54 2021 -0800 |
| tree | 7635272f574d16abb76efb6b16e0b23dcbc56773 | |
| parent | 0f8f2dc2ceb5ea63aa520bb7624aade4aad68fc3 [diff] |
Bazel: remove uses of deprecated EvalException(Location...) ...in Android native (repo) rules. Instead of putting the common information in each exception, it is added as a prefix when reporting the failure of the fetch operation. Also, add test for this prefix. Aside: I don't understand why (stackless) EvalExceptions are used for these errors, which have nothing to do with Starlark. PiperOrigin-RevId: 351361914
{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:
See CONTRIBUTING.md
