| commit | 768751c076c6d556aeba38151ac82323a1001f75 | [log] [tgz] |
|---|---|---|
| author | ilist <ilist@google.com> | Wed Jan 26 07:56:06 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 26 07:57:40 2022 -0800 |
| tree | a58fca2146a0108ea23d96d5228557ad1ebc3c08 | |
| parent | 4bf9c9d71eac23b19c9aa0aac1d26eeeec4c0015 [diff] |
Stop using rule attributes from ctx in android_lint action. The parameters and some of the logic are reorganised to match what a callee of this function would expect: pass in sources and compilation information and run the linter. Not passing in java_info makes it at least in theory possible to run linter over something that wasn't produced by other Java calls. Condition to run linter only in target configuration (not host or exec) was moved one level higher, not to confuse a potential user. Compile_action was change to return compilation information in nicer form. PiperOrigin-RevId: 424345907
{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
