Chris Parsons 9402ca881c Add a persistent bazel server between builds ... This feature is toggled on with USE_PERSISTENT_BAZEL, which is off by default. Those that opt-in will have a bazel server running between builds (with a 3hr default TTL) which will greatly improve analysis on subsequent builds. (As Bazel maintains a cache of analysis results). Bug: 266983462 Test: Manual `m nothing` runs (timing with and without the feature) Test: New integration test Test: Presubmits Change-Id: I3af4948baa0c490e9b87c48ffdbe9f67732586c7		2023-03-01 23:30:19 -05:00
..
cquery	mixed build targets need transitive tidy files	2023-02-07 16:50:30 -05:00
Android.bp	Add a persistent bazel server between builds	2023-03-01 23:30:19 -05:00
aquery.go	Handle aquery build statements in a goroutine	2023-02-15 11:29:49 -05:00
aquery_test.go	Handle aquery build statements in a goroutine	2023-02-15 11:29:49 -05:00
bazel_proxy.go	Add a persistent bazel server between builds	2023-03-01 23:30:19 -05:00
configurability.go	Fix nondeterminism in bp2build	2023-01-30 21:26:57 +00:00
constants.go	refactor Bazel variable export	2022-04-06 14:48:32 +00:00
properties.go	Merge "Fix nondeterminism in bp2build"	2023-01-30 22:58:17 +00:00
properties_test.go	Correct global excludes not always being excluded	2023-01-26 11:16:39 -05:00
testing.go	add unit test for bp2build allowlist	2022-04-14 13:31:09 +00:00