From ae133e55a0fac1eb9a0258af292c13150d6676c3 Mon Sep 17 00:00:00 2001 From: Scott Dugas Date: Mon, 3 Nov 2025 16:53:15 -0500 Subject: [PATCH] Upload the jreleaser trace logs & config We got an OutOfMemory with 4g of heap, and 211m of artifacts. This will upload the logs and config to the artifacts for investigation, in the hops it gives us something useful. I checked locally and neither appear to have any of the passwords. --- .github/workflows/release.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 6ae1a26525..1554e12a85 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -193,6 +193,13 @@ jobs: JRELEASER_MAVENCENTRAL_USERNAME: ${{ secrets.SONATYPE_USERNAME }} JRELEASER_MAVENCENTRAL_PASSWORD: ${{ secrets.SONATYPE_PASSWORD }} GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + - name: Upload jreleaser trace logs + if: always() + uses: actions/upload-artifact@v4.6.0 + with: + name: jrelease-trace + path: .out/jreleaser/* + retention-days: 1 # Post release: Update various files which reference version # Updating the yaml files has to be done after the tests complete, or it will mark tests as failing that aren't