From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

There is no property by default, just add your own manually. 

Actually better do not have test-dependent code, or you do not test what is actually used. :slightly_smiling_face:

I have enabled by default to publish Gradle scans in my convention plugin if the run is on `CI`. I have seen that it is uploading a build scan per each test. I have added to each test:

```withEnvironment(mapOf("CI" to "false"))```

Well, after checking it, it is only happening in one test, but I would expect it to happen on all tests :thinking_face:

Anyway, I am going to disable it on all tests to avoid future issues.

I see. Alternatively to having test-only-specific code in your production convention plugin code, you could for example have an init script in your tests that disables build scan publishing, or you can add `--no-scan` to the call arguments.