Skip to content

General CI

General CI #8121

Manually triggered September 20, 2024 23:35
Status Cancelled
Total duration 45m 42s
Artifacts 8

ci.yml

on: workflow_dispatch
set-condition
8s
set-condition
parachain-dynamic-contract-test
18s
parachain-dynamic-contract-test
parachain-build-dev
44m 24s
parachain-build-dev
parachain-clippy
13m 22s
parachain-clippy
parachain-unit-test
7m 29s
parachain-unit-test
parachain-runtime-test
26m 2s
parachain-runtime-test
Matrix: tee-check
Matrix: parachain-ts-test
Matrix: identity-single-worker-test
Matrix: identity-multi-worker-test
Matrix: bitacross-worker-test
push-docker
0s
push-docker
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 25 warnings
parachain-build-dev
The run was canceled by @github-actions[bot].
parachain-build-dev
Process completed with exit code 1.
Legacy key/value format with whitespace separator should not be used: tee-worker/identity/build.Dockerfile#L133
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/identity/build.Dockerfile#L134
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/
Variables should be defined before their use: tee-worker/identity/build.Dockerfile#L135
UndefinedVar: Usage of undefined variable '$LD_LIBRARY_PATH' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: tee-worker/identity/build.Dockerfile#L25
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/identity/build.Dockerfile#L26
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/identity/build.Dockerfile#L27
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/identity/build.Dockerfile#L28
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/identity/build.Dockerfile#L29
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/
Sensitive data should not be used in the ARG or ENV commands: tee-worker/identity/build.Dockerfile#L61
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SGX_COMMERCIAL_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: tee-worker/identity/build.Dockerfile#L62
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SGX_COMMERCIAL_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: tee-worker/identity/build.Dockerfile#L100
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/identity/build.Dockerfile#L101
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/bitacross/build.Dockerfile#L117
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/bitacross/build.Dockerfile#L118
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/
Variables should be defined before their use: tee-worker/bitacross/build.Dockerfile#L119
UndefinedVar: Usage of undefined variable '$LD_LIBRARY_PATH' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: tee-worker/bitacross/build.Dockerfile#L84
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/bitacross/build.Dockerfile#L85
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/
Sensitive data should not be used in the ARG or ENV commands: tee-worker/bitacross/build.Dockerfile#L57
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "SGX_COMMERCIAL_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: tee-worker/bitacross/build.Dockerfile#L26
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/bitacross/build.Dockerfile#L27
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/bitacross/build.Dockerfile#L28
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/bitacross/build.Dockerfile#L29
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/
Legacy key/value format with whitespace separator should not be used: tee-worker/bitacross/build.Dockerfile#L30
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/
Sensitive data should not be used in the ARG or ENV commands: tee-worker/bitacross/build.Dockerfile#L56
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SGX_COMMERCIAL_KEY") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
parachain-build-dev
Cancelled the workflow run from job parachain-build-dev

Artifacts

Produced during runtime
Name Size
litentry-bitacross
188 MB
litentry-identity
194 MB
litentry~litentry-parachain~C7EVCV.dockerbuild
47.4 KB
litentry~litentry-parachain~NQIRIS.dockerbuild
47.8 KB
litentry~litentry-parachain~O1Z2SR.dockerbuild
25.4 KB
litentry~litentry-parachain~POI5AN.dockerbuild
183 KB
litentry~litentry-parachain~RXGN25.dockerbuild
194 KB
litentry~litentry-parachain~W6HHS4.dockerbuild
27.5 KB