Identifying the benchmark iteration from the build under test

[remcomokveld]

It would be nice to have access to org.gradle.profiler.BuildContext#getUniqueBuildId in some way from the gradle project that is being measured. Maybe through an environment variable or by adding a gradle/system property that the build can consume?

It would be helpful to be able to capture more per-build metrics without having to write custom profilers and using a custom fork of the gradle-profiler

[gabrielfeo]

I'm not sure I understand your use case, but you may be able to achieve what you want with the existing org.gradle.profiler.* system properties that are passed to the target build. Keep in mind that they're probably considered an internal implementation detail, rather than public API. Also, consider reading them in a way that doesn't invalidate configuration caching, if you enabled cache and you expect it to be hit in your benchmark.

[remcomokveld]

The use case is that we use a build service which captures data during the build and write that to a file. After all scenarios are completed we'd like to archive those files and be able to tie them back to the individual runs.

These properties are indeed going to help with that, thanks! Would be nice if they could be considered public API

[remcomokveld]

Yeah this was indeed what I needed, thansk @gabrielfeo!

If there's no intention of making this public then this issue can be closed

[Maf1459]

It would be nice to have access to org.gradle.profiler.BuildContext#getUniqueBuildId in some way from the gradle project that is being measured. Maybe through an environment variable or by adding a gradle/system property that the build can consume?

It would be helpful to be able to capture more per-build metrics without having to write custom profilers and using a custom fork of the gradle-profiler