Create release draft #290
BillyWooocreate-release-draft.yml
on: workflow_dispatch
Matrix: build-parachain-runtime
set-release-type
0s
build-identity-worker
31m 8s
build-bitacross-worker
26m 8s
build-parachain-client
1h 38m
Matrix: parachain-ts-tests
create-release-draft
18s
Deployment protection rules
Reviewers, timers, and other rules protecting deployments in this run
| Event | Environments |
|---|---|
BillyWooo
approved
|
production and production |
Annotations
2 errors and 32 warnings
|
build-parachain-client
unable to access 'https://github.com/litentry/litentry-parachain/': Failed to connect to github.com port 443 after 135901 ms: Connection timed out
|
|
create-release-draft
Process completed with exit code 127.
|
|
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/
|
|
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#L151
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#L152
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#L153
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#L154
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#L155
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#L155
UndefinedVar: Usage of undefined variable '$PKG_CONFIG_PATH'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
|
Variables should be defined before their use:
tee-worker/bitacross/build.Dockerfile#L156
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#L156
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#L174
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#L167
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#L171
UndefinedVar: Usage of undefined variable '$PKG_CONFIG_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#L172
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#L190
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#L168
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#L169
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#L170
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#L171
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#L172
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#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#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/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
litentry-collator
Expired
|
168 MB |
|
|
litentry-parachain-runtime
Expired
|
1.52 MB |
|
|
paseo-parachain-runtime
Expired
|
1.53 MB |
|
|
rococo-parachain-runtime
Expired
|
1.53 MB |
|