Skip to content
Java CI with Gradle

Update Gradle Usage in CI #475

Sign in to view logs

Update Gradle Usage in CI

Update Gradle Usage in CI #475

Triggered via pull request January 26, 2026 16:43
@thebeanogamerthebeanogamer
opened #34
gradlefix
Status Failure
Total duration 2m 42s
Artifacts 1

gradle.yml

on: pull_request
build
2m 38s
build
dependency-submission
1m 21s
dependency-submission
javadoc
1m 10s
javadoc
Fit to window
Zoom out
Zoom in

Annotations

1 error, 2 warnings, and 1 notice
build
Process completed with exit code 1.
javadoc
Failed to restore gradle-home-v1|Linux|javadoc[04d8ed242d6e4f9366abd4632caf0523]-f8c867d7155ca30e823ae3c330aefa2621d51fa2: Error: Cache service responded with 400
dependency-submission
Failed to restore v9-gradle|Linux|dependency-submission[04d8ed242d6e4f9366abd4632caf0523]-f8c867d7155ca30e823ae3c330aefa2621d51fa2: Error: Cache service responded with 400
dependency-submission
Submitted dependency-graph-reports/java_ci_with_gradle-dependency-submission.json: The snapshot was accepted, but it is not for the default branch. It will not update dependency results for the repository.

Artifacts

Produced during runtime
Name Size Digest
resource-usage-log
3.75 KB
sha256:3c190be1eedc8ebbb9f02b42c0840923b41536de5f49c95e2a3cf8d8420eb5e5