Validation actions: correct builds off the critical path
summary
Bazel adds a mechanism that collects dummy outputs into a validation output group so lint and static-analysis actions can run off the critical path and even run in parallel with tests, letting expensive checks like Android Lint execute after normal build actions finish. Implementation reuses output groups (not aspects) to avoid extra memory and analysis cost; limitations include overt triggering (validation runs whenever a touched target contains one) and resource-driven parallelism, and the API feels clunky and needs finer-grained controls.
AI-written summary · about