ci: Add CIS benchmark check #3593
checks.yml
on: pull_request
Matrix: lint-go
unit-test
9m 1s
lint-gha
13s
pre-commit
4m 59s
lint-test-helm
4m 7s
Matrix: cis-benchmark
Matrix: e2e-quick-start
Matrix: e2e-self-hosted
Annotations
2 errors and 23 warnings
CIS Benchmark (Docker provider, Kubernetes v1.33) / e2e-test
Process completed with exit code 2.
|
CIS Benchmark (Nutanix provider, Kubernetes v1.32) / e2e-test
Process completed with exit code 2.
|
lint-test-helm
Failed to restore: Cache service responded with 422
|
lint-test-helm
Cache save failed.
|
lint-go (api)
Failed to restore: Cache service responded with 422
|
lint-go (api)
Cache save failed.
|
lint-go (api)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|
lint-go (common)
Failed to restore: Cache service responded with 422
|
lint-go (common)
Cache save failed.
|
lint-go (common)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|
pre-commit
Failed to restore: Cache service responded with 422
|
pre-commit
Cache save failed.
|
lint-go (.)
Failed to restore: Cache service responded with 422
|
lint-go (.)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|
unit-test
Failed to restore: Cache service responded with 422
|
unit-test
Cache save failed.
|
CIS Benchmark (Docker provider, Kubernetes v1.33) / e2e-test
Failed to restore: Cache service responded with 422
|
e2e-quick-start (Docker provider, Kubernetes v1.31) / e2e-test
Failed to restore: Cache service responded with 422
|
e2e-quick-start (Docker provider, Kubernetes v1.30) / e2e-test
Failed to restore: Cache service responded with 422
|
e2e-quick-start (Docker provider, Kubernetes v1.32) / e2e-test
Failed to restore: Cache service responded with 422
|
e2e-quick-start (Docker provider, Kubernetes v1.33) / e2e-test
Failed to restore: Cache service responded with 422
|
CIS Benchmark (Nutanix provider, Kubernetes v1.32) / e2e-test
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.322.0. Please update to the latest version 2.323.0
|
e2e-self-hosted (Docker provider, Kubernetes v1.33) / e2e-test
Failed to restore: Cache service responded with 422
|
e2e-self-hosted (Docker provider, Kubernetes v1.32) / e2e-test
Failed to restore: Cache service responded with 422
|
e2e-self-hosted (Docker provider, Kubernetes v1.31) / e2e-test
Failed to restore: Cache service responded with 422
|