This message was deleted.

If you apply the Gradle Enterprise Gradle plugin you can configure these settings, it works for both Gradle Enterprise and scans.gradle.com There's a section in there on Controlling when build scans are published which has multiple ways of configuring this, like always publishing when CI is running

Thanks, but I should have mentioned that I'm not using the enterprise plugin.

When you do

--scan

the enterprise plugin is automatically applied. So technically you cannot use build scans without that plugin. (I don’t think the

--no-scan

option can be used in a useful way without applying the plugin first.) This is also why adding

--scan

to a project that does not apply the plugin explicitly changes the plugin classpath. Which potentially leads to Gradle rebuilding a lot of things. I’d always apply the enterprise plugin if the project uses build scans on a regular basis.

Which potentially leads to Gradle rebuilding a lot of things.

Oh, wow, I wasn't aware of that. Thanks for pointing that out.

I think so

We are doing exactly this ourselves, it’s just a few extra lines in your configuration: We have a boolean property

gradleScanPublishAlways

in our gradle.properties file that is read when applying the gradle enterprise plugin and used with the

publishAlwaysIf(boolean)

option