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:
@@ -87,6 +87,8 @@ type CmdArgs struct {
|
||||
BazelModeDev bool
|
||||
BazelModeStaging bool
|
||||
BazelForceEnabledModules string
|
||||
|
||||
UseBazelProxy bool
|
||||
}
|
||||
|
||||
// Build modes that soong_build can run as.
|
||||
@@ -251,6 +253,10 @@ type config struct {
|
||||
// specified modules. They are passed via the command-line flag
|
||||
// "--bazel-force-enabled-modules"
|
||||
bazelForceEnabledModules map[string]struct{}
|
||||
|
||||
// If true, for any requests to Bazel, communicate with a Bazel proxy using
|
||||
// unix sockets, instead of spawning Bazel as a subprocess.
|
||||
UseBazelProxy bool
|
||||
}
|
||||
|
||||
type deviceConfig struct {
|
||||
@@ -442,6 +448,8 @@ func NewConfig(cmdArgs CmdArgs, availableEnv map[string]string) (Config, error)
|
||||
mixedBuildDisabledModules: make(map[string]struct{}),
|
||||
mixedBuildEnabledModules: make(map[string]struct{}),
|
||||
bazelForceEnabledModules: make(map[string]struct{}),
|
||||
|
||||
UseBazelProxy: cmdArgs.UseBazelProxy,
|
||||
}
|
||||
|
||||
config.deviceConfig = &deviceConfig{
|
||||
|
Reference in New Issue
Block a user