Extract test results when there are failures about actions

[tbroyer]

I use something similar to the following in my workflows:

      - name: Store reports
        if: failure()
        uses: actions/upload-artifact@v3
        with:
          name: reports
          path: |
            **/build/reports/
            **/build/test-results/

See https://docs.github.com/en/actions/learn-github-actions/expressions#status-check-functions

Note that the name is important if you have more than one Gradle invocation in the whole workflow (e.g. in a matrix build).
Also, what if you setup Gradle using the action, then run Gradle twice, e.g., with different project properties, in the same job; how should the gradle-build-action archive those? Under which names?
Should it archive only on failure? It's sometimes useful to check successful reports to see which tests were ignored and which were run.

To me, that's not the role of the gradle-build-action to do that, or that'll require it to be much more complex, if only in configurability.

[bigdaz]

Related to gradle/gradle-build-action#98

[hfhbd]

Is this Kotlin MPP specific? Build scans contain JUnit test results.

[hartmut-co-uk]

PS: There are other OSS actions available already, maybe it's sufficient to provide references?

• https://github.com/marketplace/actions/junit-report-action
• https://github.com/marketplace/actions/test-reporter

(there may be others...)

[oleg-nenashev]

I think it would be nice to at least document the solution