This message was deleted.

no

I feel this too, would love to have more detailed insight into our complex builds but inhouse IT regulations won't let the scan past our proxy. I guess an option would be to deploy a Gradle Enterprise server on-site and publish the scans there, but this comes with it's own batch of red tape issues

Heck, I'd be happy enough even having to spin up enterprise server locally and just publish to that (without any networking) just to see the scand 😄

its worth it 🙂

it would actually be nice to be able to do this, as GE customers, to capture scans when in

--offline

mode and then publish them later. Using offline for gradle-profiler helps make for more repeatable metrics, but we often want to look at scans later, especially if there were failures

buildScanPublishPrevious

is not good enough because it only captures the most recent build

@Big Chungus did you look into the profile report? You could generate the local HTML report and get your CI server to archive it ./gradlew build --profile https://docs.gradle.org/current/userguide/performance.html#profile_report

I did not. Thanks for bringing it up.