ci: Enable Gradle stacktraces in the release workflow

When artifact signing fails, the reason can typically only be found by printing the stacktrace. Enable stacktraces to help with debugging signing issues in future. Signed-off-by: Martin Nonnenmacher <[email protected]>
eclipse-apoapsis · Oct 9, 2024 · 6677986 · 6677986
1 parent 52c9958
commit 6677986
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -45,7 +45,7 @@ jobs:
         # https://keyserver.ubuntu.com/pks/lookup?search=apoapsis-dev&fingerprint=on&op=index
         ORG_GRADLE_PROJECT_signingInMemoryKeyId: 437c0602
         ORG_GRADLE_PROJECT_signingInMemoryKeyPassword: ${{ secrets.ORG_GPG_PASSPHRASE }}
-      run: ./gradlew --no-configuration-cache publishAndReleaseToMavenCentral
+      run: ./gradlew --stacktrace --no-configuration-cache publishAndReleaseToMavenCentral
 
     - name: Generate Release Notes
       # Temporary implementation for the very first release. The release notes for this will be written by hand as they