CD - Syft #420
rasswanth-scd-syft.yml
on: schedule
release-checks
8s
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-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-notebook-scenario-k8s-sync
Matrix: call-pr-tests-stack / pr-tests-scenarios-migrations
Matrix: call-pr-tests-stack / pr-tests-simulation-scenario-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-scenario-sync
Matrix: call-pr-tests-syft / pr-tests-syft-notebook-scenario
Matrix: call-pr-tests-syft / pr-tests-syft-notebook-single-container
Matrix: call-pr-tests-syft / pr-tests-syft-scenario-sync
Matrix: call-pr-tests-syft / pr-tests-syft-scenario
Matrix: call-pr-tests-syft / pr-tests-syft-security
Matrix: call-pr-tests-syft / pr-tests-syft-unit
Matrix: build-and-push-docker-images
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
Annotations
30 errors and 68 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.11)
Process completed with exit code 2.
|
|
call-cd-post-release-tests / syft-install-check (ubuntu-latest, 3.12)
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_12" failed.
|
|
call-cd-post-release-tests / syft-install-check (macos-latest, 3.12)
The job was canceled because "ubuntu-latest_3_12" failed.
|
|
call-cd-post-release-tests / syft-install-check (macos-14, 3.12)
The job was canceled because "ubuntu-latest_3_12" failed.
|
|
call-cd-post-release-tests / syft-install-check (macos-latest, 3.10)
The job was canceled because "ubuntu-latest_3_12" failed.
|
|
call-cd-post-release-tests / syft-unit-tests (ubuntu-latest, 3.12)
The job was canceled because "ubuntu-latest_3_11" failed.
|
|
call-cd-post-release-tests / syft-unit-tests (macos-latest, 3.12)
The job was canceled because "ubuntu-latest_3_11" 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 (ubuntu-latest, 3.10)
The job was canceled because "ubuntu-latest_3_11" failed.
|
|
call-cd-post-release-tests / syft-unit-tests (ubuntu-latest, 3.10)
The operation was canceled.
|
|
call-cd-post-release-tests / syft-unit-tests (macos-latest, 3.10)
The job was canceled because "ubuntu-latest_3_11" failed.
|
|
call-cd-post-release-tests / syft-unit-tests (macos-latest, 3.10)
The operation was canceled.
|
|
call-cd-post-release-tests / syft-install-check (ubuntu-latest, 3.11)
The job was canceled because "ubuntu-latest_3_12" failed.
|
|
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 (windows-latest, 3.12)
The job was canceled because "ubuntu-latest_3_12" 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.10)
The job was canceled because "ubuntu-latest_3_12" 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 (macos-14, 3.10)
The job was canceled because "ubuntu-latest_3_12" failed.
|
|
call-cd-post-release-tests / syft-install-check (macos-14, 3.10)
The operation was canceled.
|
|
call-cd-post-release-tests / syft-install-check (macos-14, 3.11)
The job was canceled because "ubuntu-latest_3_12" failed.
|
|
call-cd-post-release-tests / syft-install-check (macos-14, 3.11)
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_11" failed.
|
|
call-cd-post-release-tests / syft-unit-tests (macos-latest, 3.11)
The operation was canceled.
|
|
call-cd-post-release-tests / syft-install-check (ubuntu-latest, 3.10)
The job was canceled because "ubuntu-latest_3_12" 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 (windows-latest, 3.11)
The job was canceled because "ubuntu-latest_3_12" failed.
|
|
call-cd-post-release-tests / syft-install-check (windows-latest, 3.11)
The operation was canceled.
|
|
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-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-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-syft / pr-tests-syft-scenario (ubuntu-latest, 3.12, python, False)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-syft / pr-tests-syft-scenario (3.10, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-syft / pr-tests-syft-scenario (3.12, ubuntu-latest, python, True)
'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-scenario (3.11, ubuntu-latest, python)
'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-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-unit (3.10, ubuntu-latest)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-stack / pr-tests-scenarios-migrations (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-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-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-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-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-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-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 (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 (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.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-scenario-sync (ubuntu-latest, 3.12, python, False)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-syft / pr-tests-syft-scenario-sync (3.11, ubuntu-latest, python)
'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
|
|
call-pr-tests-syft / pr-tests-syft-scenario-sync (3.12, ubuntu-latest, python, True)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-stack / pr-tests-simulation-scenario-k8s (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-scenario-sync (3.10, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-stack / pr-tests-migrations-k8s (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-scenario-sync (3.12, ubuntu-latest, python, True)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.11, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (ubuntu-latest, 3.12, python, False)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-syft / pr-tests-syft-notebook-scenario-sync (3.10, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-syft / pr-tests-syft-notebook-scenario (ubuntu-latest, 3.12, python, False)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.10, ubuntu-latest, python)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.12, ubuntu-latest, python, True)
'before' field is missing in event payload - changes will be detected from last commit
|
|
call-pr-tests-syft / pr-tests-syft-notebook-scenario (3.11, ubuntu-latest, python)
'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-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-scenario-k8s-sync (ubuntu-latest, 3.12)
'before' field is missing in event payload - changes will be detected from last commit
|
|
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/
|
|
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/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/
|
|
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 "POSTGRESQL_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/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/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/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/
|
|
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 "POSTGRESQL_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/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/
|
|
call-cd-post-release-tests / syft-unit-tests (ubuntu-latest, 3.11)
Cache not found for keys: Linux-pip-py3.11-, Linux-pip-py3.11-
|
|
call-cd-post-release-tests / syft-install-check (ubuntu-latest, 3.12)
Cache not found for keys: Linux-pip-py3.12-, Linux-pip-py3.12-
|
|
call-cd-post-release-tests / syft-unit-tests (macos-latest, 3.12)
Cache not found for keys: macOS-pip-py3.12-, macOS-pip-py3.12-
|
|
call-cd-post-release-tests / syft-install-check (ubuntu-latest, 3.11)
Cache not found for keys: Linux-pip-py3.11-, Linux-pip-py3.11-
|
|
call-cd-post-release-tests / syft-install-check (macos-14, 3.11)
Cache not found for keys: macOS-pip-py3.11-, macOS-pip-py3.11-
|
|
call-cd-post-release-tests / syft-install-check (ubuntu-latest, 3.10)
Cache not found for keys: Linux-pip-py3.10-, Linux-pip-py3.10-
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
OpenMined~PySyft~17UXT7.dockerbuild
|
45.4 KB |
|
|
OpenMined~PySyft~1NLEJD.dockerbuild
|
41.9 KB |
|
|
OpenMined~PySyft~5DA8XT.dockerbuild
|
44.1 KB |
|
|
OpenMined~PySyft~6MVJOL.dockerbuild
|
56.8 KB |
|
|
OpenMined~PySyft~AAK0BX.dockerbuild
|
63.1 KB |
|
|
OpenMined~PySyft~BDIQWO.dockerbuild
|
46.4 KB |
|
|
OpenMined~PySyft~KKQH0O.dockerbuild
|
42.1 KB |
|
|
OpenMined~PySyft~P1ST1H.dockerbuild
|
63.1 KB |
|
|
OpenMined~PySyft~RWCX8A.dockerbuild
|
57.9 KB |
|
|
OpenMined~PySyft~ST62P6.dockerbuild
|
44.3 KB |
|
|
OpenMined~PySyft~XBT9N1.dockerbuild
|
52.1 KB |
|
|
digests-0.9.6-beta.1-amd64
Expired
|
1.49 KB |
|
|
digests-0.9.6-beta.1-arm64
Expired
|
1.22 KB |
|