Skip to content

Develocity - Publish Maven Build Scans #28535

Develocity - Publish Maven Build Scans

Develocity - Publish Maven Build Scans #28535

Triggered via workflow run May 28, 2026 18:49
@lucamoltenilucamolteni
completed 8750950
Status Success
Total duration 19m 38s
Artifacts 1
publish-build-scans
7m 33s
publish-build-scans
Fit to window
Zoom out
Zoom in

Annotations

1 warning and 1 notice
publish-build-scans
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-java@v4, gradle/develocity-actions/maven-publish-build-scan@974e8dbcbda40db6828fc35f349c80a7c0e71529, gradle/develocity-actions/setup-maven@974e8dbcbda40db6828fc35f349c80a7c0e71529. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
publish-build-scans
Injecting build scans into build report

Artifacts

Produced during runtime
Name Size Digest
build-metadata.json
3.81 KB
sha256:5312c6c85d7bac5304194cbbf8f28d71a46a1643ea51e0652652bc55d5a49599