This message was deleted.

We pass these parameters to the build under test: https://github.com/gradle/gradle-profiler/blob/a3805fc047f011e7fdd47671225bf0d6e3cdddae/src/main/java/org/gradle/profiler/BuildUnderTestInvoker.java#L55-L59

Thanks!

In case you’re benchmarking a scenario with configuration cache enabled, be aware that reading some of these these properties on each build will cause a cache miss since they always change e.g. “build number” (scenario name is OK)

@Gabriel Feo we're not using configuration cache yet. But, if I just read the property via

System.properties['org.gradle.profiler.number']

and pass it in a build scan tag, will it change the configuration cache input?

Yes, because if you read it Gradle understands that the configuration of your build varies according to that variable. It becomes an input to the configuration. So whenever it changes Gradle decides it cannot use the cached configuration because it relied on ‘profiler.number == 2’ which it is now ‘== 3’