Guard include scanner against null grepIncludes The grepIncludes artifact may be null if the owning rule doesn't have a $grep_includes attribute (see CppHelper.getGrepIncludes). This seems to be intentional. However, the remote include scanner requires that grepIncludes is *not* null, so we need to safe-guard against it. Unfortunately, this is brittle, because accidentally misspelling or removing the attributes makes all grep operations fall back to the built-in implementation. PiperOrigin-RevId: 277499382
{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
