Open warting opened 5 days ago
Thanks for the report. We have test coverage for this combination of versions, so there must be something about your project that is causing this to fail.
The Job Summary functionality works via Gradle init scripts, which are automatically injected into Gradle User Home. These init-scripts write a results file to $RUNNER_TEMP/.build-results
.
Can you please check the following:
$RUNNER_TEMP/.build-results
directory? cat
all of the .json
files in .build-results
to check contents. These JSON files should contain the Build Scan link but I assume in your case they do not.The added step would look something like this:
- name: Print build results
working-directory: ${{ env.RUNNER_TEMP }}
shell: bash
run: |
echo "RUNNER_TEMP = $RUNNER_TEMP"
ls -la $RUNNER_TEMP
ls -la $RUNNER_TEMP/.build-results
find $RUNNER_TEMP/.build-results -name *.json -type f -exec cat {} \;
echo ""
Once I have a better feel for where this might be failing, I can publish a release with some additional logging to help dig deeper.
Build scans is published but setup gradle does not retreive the url.
Versions used: