Skip to content

feat(restic): support for using an existing pvc as a repository #4178

feat(restic): support for using an existing pvc as a repository

feat(restic): support for using an existing pvc as a repository #4178

Triggered via pull request October 18, 2024 12:39
Status Failure
Total duration 1h 15m 45s
Artifacts 3

operator.yml

on: pull_request
Lint
54s
Lint
Auto Generated Files Check
1m 8s
Auto Generated Files Check
Test-operator
6m 32s
Test-operator
Build-custom-scorecard-tests
3m 34s
Build-custom-scorecard-tests
Matrix: End-to-end
Successful e2e tests
0s
Successful e2e tests
Containers should be pushed
0s
Containers should be pushed
Push custom scorecard container to registry  /  push-to-registry
Push custom scorecard container to registry / push-to-registry
Push operator container to registry  /  push-to-registry
Push operator container to registry / push-to-registry
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Lint: test-e2e/test_restic_manual_PVC_copy_trigger.yml#L63
63:1 [empty-lines] too many blank lines (3 > 2)
Lint
Process completed with exit code 1.
End-to-end (1.20.15)
Process completed with exit code 2.
End-to-end (1.26.6)
Process completed with exit code 2.
End-to-end (1.25.11)
Process completed with exit code 2.
End-to-end (1.27.3)
Process completed with exit code 2.
End-to-end (1.30.0)
Process completed with exit code 2.
End-to-end (1.29.0)
Process completed with exit code 2.
End-to-end (1.28.0)
Process completed with exit code 2.
End-to-end (1.31.0)
Process completed with exit code 2.

Artifacts

Produced during runtime
Name Size
kubectl-volsync
23.2 MB
volsync-custom-scorecard-tests-container
562 MB
volsync-operator
271 MB