From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

gonna test it out! <https://github.com/autonomousapps/dependency-analysis-gradle-plugin/pull/1088>

(this just bumps to the prerelease. Will do more stuff with it next)

Daz, the documentation for that github action is sublime. I love the detail :heart:

<@UAF4ZBBBN> is there a simple way to use <https://github.com/gradle/gradle-build-action#build-scan-link-as-step-output|this technique> when there are multiple Gradle steps? I would like a failure on any of those steps to result in commenting on the PR with the build scan url. Would I give all the steps the same `id`?

I don't think multiple steps can share the same `id`. The simplest solution I can think for multiple Gradle steps is to have a single "PR comment" step, that has `if: failure()` and adds the Build Scan URL for all Gradle steps on failure.

yeah... I wish I could include the scan for _only_ the failed step

I probably could if I were willing to write a more complex step... I can kind of see how I'd do it. But not sure it's worth the effort. Thanks!

<@UES7RHBDZ> Based on your question/comment, I've added a new feature to `gradle-build-action@v3-prerelease`. The action is now able to automatically add a pull-request comment with the content of the Job Summary. This includes a table of all Gradle executions as well as links to any published build scans.
See <https://github.com/gradle/gradle-build-action?tab=readme-ov-file#adding-job-summary-as-a-pull-request-comment> for details.