"name":"TestDistribution"
				},
				"subprojects":[
					"launcher",
					"time",
					"logging-api",
					"kotlin-dsl-plugins",
					"serialization",
					"toolchains-jvm-shared",
					"docs-asciidoctor-extensions-base",
					"internal-instrumentation-processor",
					"security",
					"input-tracking",
					"base-ide-plugins"
				]
			},
			{
				"parallelizationMethod":{

    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "docs",
    "path": "platforms/documentation/docs",
    "unitTests": true,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "docs-asciidoctor-extensions",
    "path": "platforms/documentation/docs-asciidoctor-extensions",
    "unitTests": false,
    "functionalTests": false,

The build process state also includes state that is tied to a particular Gradle user home directory.
When that directory changes between Gradle invocations, the state is discarded and recreated.
Typically, the Gradle user home directory does not change for a given process, so this is effectively process state.

The build process state is managed by the `BuildProcessState` class. An instance is created once for a given process.

### Build session state