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
This commit is contained in:
@@ -81,6 +81,7 @@ func init() {
|
||||
flag.BoolVar(&cmdlineArgs.BazelMode, "bazel-mode", false, "use bazel for analysis of certain modules")
|
||||
flag.BoolVar(&cmdlineArgs.BazelModeStaging, "bazel-mode-staging", false, "use bazel for analysis of certain near-ready modules")
|
||||
flag.BoolVar(&cmdlineArgs.BazelModeDev, "bazel-mode-dev", false, "use bazel for analysis of a large number of modules (less stable)")
|
||||
flag.BoolVar(&cmdlineArgs.UseBazelProxy, "use-bazel-proxy", false, "communicate with bazel using unix socket proxy instead of spawning subprocesses")
|
||||
|
||||
// Flags that probably shouldn't be flags of soong_build, but we haven't found
|
||||
// the time to remove them yet
|
||||
|
Reference in New Issue
Block a user