Skip to content
JFrog CLI Security Tests

Support maven cli for curation cli cmd. #82

Sign in to view logs

Support maven cli for curation cli cmd.

Support maven cli for curation cli cmd. #82

Re-run triggered February 13, 2024 12:16
@attiasasattiasas
#13
Status Failure
Total duration 2m 47s
Artifacts –

test.yml

on: pull_request_target
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
test (windows)
unable to create file tests/testdata/projects/package-managers/maven/maven-curation/.jfrog/curation/cache/maven/com/google/guava/listenablefuture/9999.0-empty-to-avoid-conflict-with-guava/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar: Filename too long
test (windows)
unable to create file tests/testdata/projects/package-managers/maven/maven-curation/.jfrog/curation/cache/maven/com/google/guava/listenablefuture/9999.0-empty-to-avoid-conflict-with-guava/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar.sha1: Filename too long
test (windows)
unable to create file tests/testdata/projects/package-managers/maven/maven-curation/.jfrog/curation/cache/maven/com/google/guava/listenablefuture/9999.0-empty-to-avoid-conflict-with-guava/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.pom: Filename too long
test (windows)
unable to create file tests/testdata/projects/package-managers/maven/maven-curation/.jfrog/curation/cache/maven/com/google/guava/listenablefuture/9999.0-empty-to-avoid-conflict-with-guava/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.pom.sha1: Filename too long
test (windows)
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 1
test (macos)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/setup-node@v3, actions/setup-java@v3, nuget/setup-nuget@v1, actions/setup-dotnet@v3, actions/setup-python@v4, gradle/gradle-build-action@v2, actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
test (ubuntu)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/setup-node@v3, actions/setup-java@v3, nuget/setup-nuget@v1, actions/setup-dotnet@v3, actions/setup-python@v4, gradle/gradle-build-action@v2, actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
test (windows)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/setup-node@v3, actions/setup-java@v3, nuget/setup-nuget@v1, actions/setup-dotnet@v3, actions/setup-python@v4, gradle/gradle-build-action@v2, actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.