From f8c7f760b1872b5c7b4b0188bbe493523fbd1add Mon Sep 17 00:00:00 2001 From: Daz DeBoer Date: Fri, 2 May 2025 08:22:31 -0600 Subject: [PATCH] Mention that `build-scan-publish` does not force publishing --- docs/setup-gradle.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/setup-gradle.md b/docs/setup-gradle.md index 6dc827f3..40d574c8 100644 --- a/docs/setup-gradle.md +++ b/docs/setup-gradle.md @@ -753,6 +753,9 @@ To publish to https://scans.gradle.com, you must specify in your workflow that y run: ./gradlew build ``` +If your build is configured to [publish on demand](https://docs.gradle.com/develocity/gradle-plugin/current/#publishing_on_demand) +using `onlyIf { false }`, setting `build-scan-publish: true` will not force a scan to be published. + ## Managing Develocity access keys Develocity access keys are long-lived, creating risks if they are leaked. To mitigate this risk this,