actions/gradle
1
0
Fork 0
mirror of https://github.com/gradle/actions.git synced 2025-08-19 07:21:28 +08:00
Code Issues Packages Projects Releases Wiki Activity

Mention that build-scan-publish does not force publishing

Browse Source
This commit is contained in:
Daz DeBoer 2025-05-02 08:22:31 -06:00 committed by GitHub
parent be44eafdb5
commit f8c7f760b1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/setup-gradle.md
View File

@ -753,6 +753,9 @@ To publish to https://scans.gradle.com, you must specify in your workflow that y
run: ./gradlew build 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 ## Managing Develocity access keys
Develocity access keys are long-lived, creating risks if they are leaked. To mitigate this risk this, Develocity access keys are long-lived, creating risks if they are leaked. To mitigate this risk this,