Skip to content
CD - Syft

CD - Syft #367

Sign in to view logs

CD - Syft

CD - Syft #367

Re-run triggered August 28, 2024 15:16
@shubham3121shubham3121
⁠ 8ff8548
dev
Status Failure
Total duration 34s
Artifacts 13

cd-syft.yml

on: schedule
release-checks
7s
release-checks
Matrix: call-pr-tests-linting / pr-tests-linting
Matrix: call-pr-tests-stack / pr-syft-image-test
Matrix: call-pr-tests-stack / pr-tests-integration-k8s
Matrix: call-pr-tests-stack / pr-tests-migrations
Matrix: call-pr-tests-stack / pr-tests-notebook-k8s
Matrix: call-pr-tests-stack / pr-tests-syft-integration
Matrix: call-pr-tests-syft / pr-tests-syft-notebook-python
Matrix: call-pr-tests-syft / pr-tests-syft-notebook-single-container
Matrix: call-pr-tests-syft / pr-tests-syft-security
Matrix: call-pr-tests-syft / pr-tests-syft-unit
Matrix: build-and-push-docker-images
merge-docker-images
11s
merge-docker-images
deploy-syft
6m 43s
deploy-syft
Matrix: call-cd-post-release-tests / notebook-test-k8s-k3d
Matrix: call-cd-post-release-tests / syft-install-check
Matrix: call-cd-post-release-tests / syft-unit-tests
Fit to window
Zoom out
Zoom in

Annotations

31 errors and 47 warnings
call-pr-tests-syft / pr-tests-syft-unit (windows-latest, 3.12)
Process completed with exit code 1.
call-cd-post-release-tests / syft-unit-tests (ubuntu-latest, 3.10)
Process completed with exit code 2.
call-cd-post-release-tests / syft-unit-tests (macos-latest, 3.12)
The job was canceled because "ubuntu-latest_3_10" failed.
call-cd-post-release-tests / syft-unit-tests (macos-latest, 3.12)
Process completed with exit code 2.
call-cd-post-release-tests / syft-unit-tests (macos-latest, 3.11)
The job was canceled because "ubuntu-latest_3_10" failed.
call-cd-post-release-tests / syft-unit-tests (macos-latest, 3.11)
Process completed with exit code 2.
call-cd-post-release-tests / syft-install-check (ubuntu-latest, 3.11)
Process completed with exit code 2.
call-cd-post-release-tests / syft-install-check (ubuntu-latest, 3.10)
The job was canceled because "ubuntu-latest_3_11" failed.
call-cd-post-release-tests / syft-install-check (ubuntu-latest, 3.10)
Process completed with exit code 2.
call-cd-post-release-tests / syft-install-check (macos-latest, 3.11)
The job was canceled because "ubuntu-latest_3_11" failed.
call-cd-post-release-tests / syft-install-check (macos-14, 3.10)
The job was canceled because "ubuntu-latest_3_11" failed.
call-cd-post-release-tests / syft-install-check (macos-14, 3.11)
The job was canceled because "ubuntu-latest_3_11" failed.
call-cd-post-release-tests / syft-install-check (macos-14, 3.12)
The job was canceled because "ubuntu-latest_3_11" failed.
call-cd-post-release-tests / syft-install-check (macos-latest, 3.12)
The job was canceled because "ubuntu-latest_3_11" failed.
call-cd-post-release-tests / syft-install-check (macos-latest, 3.12)
Process completed with exit code 2.
call-cd-post-release-tests / syft-install-check (macos-latest, 3.10)
The job was canceled because "ubuntu-latest_3_11" failed.
call-cd-post-release-tests / syft-install-check (macos-latest, 3.10)
Process completed with exit code 2.
call-cd-post-release-tests / syft-unit-tests (ubuntu-latest, 3.12)
The job was canceled because "ubuntu-latest_3_10" failed.
call-cd-post-release-tests / syft-unit-tests (ubuntu-latest, 3.12)
The operation was canceled.
call-cd-post-release-tests / syft-unit-tests (macos-latest, 3.10)
The job was canceled because "ubuntu-latest_3_10" failed.
call-cd-post-release-tests / syft-unit-tests (ubuntu-latest, 3.11)
The job was canceled because "ubuntu-latest_3_10" failed.
call-cd-post-release-tests / syft-unit-tests (macos-latest, 3.10)
The operation was canceled.
call-cd-post-release-tests / syft-unit-tests (ubuntu-latest, 3.11)
The operation was canceled.
call-cd-post-release-tests / syft-install-check (windows-latest, 3.10)
The job was canceled because "ubuntu-latest_3_11" failed.
call-cd-post-release-tests / syft-install-check (windows-latest, 3.10)
The operation was canceled.
call-cd-post-release-tests / syft-install-check (windows-latest, 3.12)
The job was canceled because "ubuntu-latest_3_11" failed.
call-cd-post-release-tests / syft-install-check (windows-latest, 3.12)
The operation was canceled.
call-cd-post-release-tests / syft-install-check (windows-latest, 3.11)
The job was canceled because "ubuntu-latest_3_11" failed.
call-cd-post-release-tests / syft-install-check (windows-latest, 3.11)
The operation was canceled.
call-cd-post-release-tests / syft-install-check (ubuntu-latest, 3.12)
The job was canceled because "ubuntu-latest_3_11" failed.
call-cd-post-release-tests / syft-install-check (ubuntu-latest, 3.12)
The operation was canceled.
call-pr-tests-syft / pr-tests-syft-notebook-single-container (ubuntu-latest, 3.10, remote, api/0.8)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-single-container (ubuntu-latest, 3.11, remote, api/0.8)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-python (ubuntu-latest, 3.12, python, tutorials, False)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-python (macos-latest, 3.12, python, tutorials, False)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-single-container (ubuntu-latest, 3.12, remote, api/0.8)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-security (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-python (3.11, ubuntu-latest, python, tutorials)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-python (3.10, ubuntu-latest, python, tutorials)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-python (3.10, ubuntu-latest, python, tutorials)
Attempt 1 failed. Reason: Child_process exited with error code 2
call-pr-tests-syft / pr-tests-syft-unit (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-notebook-python (3.12, ubuntu-latest, python, tutorials, True)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-unit (windows-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-unit (macos-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-unit (3.10, ubuntu-latest)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-syft / pr-tests-syft-unit (3.11, ubuntu-latest)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-stack / pr-syft-image-test (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-stack / pr-tests-migrations (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-stack / pr-tests-integration-k8s (ubuntu-latest, 3.12, frontend network container_workload)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-stack / pr-tests-notebook-k8s (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
call-pr-tests-stack / pr-tests-syft-integration (ubuntu-latest, 3.12, local_server)
'before' field is missing in event payload - changes will be detected from last commit
Legacy key/value format with whitespace separator should not be used: packages/grid/frontend/frontend.dockerfile#L4
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: packages/grid/frontend/frontend.dockerfile#L37
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/frontend/frontend.dockerfile#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/frontend/frontend.dockerfile#L25
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/frontend/frontend.dockerfile#L32
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/enclave/attestation/attestation.dockerfile#L7
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/backend/backend.dockerfile#L48
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Sensitive data should not be used in the ARG or ENV commands: packages/grid/backend/backend.dockerfile#L70
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "DEFAULT_ROOT_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: packages/grid/backend/backend.dockerfile#L70
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "STACK_API_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: packages/grid/backend/backend.dockerfile#L70
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "MONGO_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/backend/backend.dockerfile#L12
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/rathole/rathole.dockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/syft-client/syft.Dockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/syft-client/syft.Dockerfile#L24
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/syft-client/syft.Dockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/syft-client/syft.Dockerfile#L24
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/backend/backend.dockerfile#L12
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/backend/backend.dockerfile#L48
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Sensitive data should not be used in the ARG or ENV commands: packages/grid/backend/backend.dockerfile#L70
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "DEFAULT_ROOT_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: packages/grid/backend/backend.dockerfile#L70
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "STACK_API_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: packages/grid/backend/backend.dockerfile#L70
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "MONGO_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/rathole/rathole.dockerfile#L5
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/frontend/frontend.dockerfile#L32
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: packages/grid/frontend/frontend.dockerfile#L4
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: packages/grid/frontend/frontend.dockerfile#L37
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/frontend/frontend.dockerfile#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: packages/grid/frontend/frontend.dockerfile#L25
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/