Closed pkoenig10 closed 1 month ago
👍 I think that's fair. I think for the most part, a lot of this can go away once we use configuration cache safe providers. Then we don't have to worry about build service's or random caches ourselves as gradle should do it for us once at the start of the build.
Thanks for putting this together.
Released 3.1.0
The acute motivation for this PR is to avoid the deprecation warnings when modifying the legacy
gradleEnterprise
.`My original intention was simply to modify
BuildScanPluginInterop
to also support thedevelocity
plugin. However, while testing I noticed thatBuildScanPluginInterop
is simply broken. The reported value is always zero because the code that runs the tasks uses a differentGitVersionCacheService
instance than the one used to record the custom values.I think this has been broken for quite a while. Given that no one has noticed, it is clearly not that important. Thus, it seemed better to just remove the code rather than "fix" code that was just broken anyways.