chore(ci): move to GitHub actions #10
bassrockuser-api.yml
on: pull_request
test-integrations
/
main
4m 53s
build-and-push-image
/
pull-request
1m 46s
build-and-push-image
/
development
0s
build-and-push-image
/
production
0s
Annotations
5 warnings
|
Sensitive data should not be used in the ARG or ENV commands:
Dockerfile#L14
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SENTRY_AUTH_TOKEN")
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:
Dockerfile#L39
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SENTRY_AUTH_TOKEN")
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:
Dockerfile#L63
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SENTRY_AUTH_TOKEN")
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:
Dockerfile#L121
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:
Dockerfile#L126
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/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
Pocket~pocket-monorepo~VAOKZM.dockerbuild
Expired
|
37 KB |
|