Can't override javaHome for GradleBuildConfigurationReader

[joshfriend]

GradleBuildConfigurationReader.readConfiguration() invokes a gradle build with the help task to generate the GradleBuildConfiguration. (For the project I am profiling, this takes several minutes of configuration time to perform. Is it possible to shorten this time it takes to resolve the gradle version and read the build configuration?)

gradle-profiler/src/main/java/org/gradle/profiler/DefaultGradleBuildConfigurationReader.java

Lines 126 to 138 in af476ee

	new ToolingApiGradleClient(connection).runTasks(ImmutableList.of("help"), ImmutableList.of("-I", initScript.getAbsolutePath()), ImmutableList.of());
	BuildDetails buildDetails = readBuildDetails();
	JavaEnvironment javaEnvironment = buildEnvironment.getJava();
	List<String> allJvmArgs = new ArrayList<>(javaEnvironment.getJvmArguments());
	allJvmArgs.addAll(readSystemPropertiesFromGradleProperties());
	boolean usesAnyScanPlugin = buildDetails.usesAnyScanPlugin();
	version = new GradleBuildConfiguration(
	GradleVersion.version(buildEnvironment.getGradle().getGradleVersion()),
	new File(buildDetails.getGradleHome()),
	javaEnvironment.getJavaHome(),
	allJvmArgs,
	usesAnyScanPlugin
	);

I cannot override the value of javaHome for this gradle execution, so it defaults to JAVA_HOME which is set to jdk11 in the environment I run these tests in. We would like to enforce JDK 17 for this project by throwing an error when a developer invokes a build with jdk11 to avoid more confusing errors that may happen later in the build, but this means that the project is no longer compatible with profiler.

I'm working on updating the build environment where profiling is run, but it seems like this should be possible to override.