Skip to content
build and publish release image

v0.0.5 #7

Sign in to view logs

v0.0.5

v0.0.5 #7

Triggered via release November 12, 2024 07:08
@matoushavlenamatoushavlena
released v0.0.5
Status Success
Total duration 50m 35s
Artifacts 1

publish-release-image.yml

on: release
build-and-push
50m 25s
build-and-push
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L40
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "AUTH_JWKS_ENDPOINT") 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#L41
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "DUMMY_JWT_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#L48
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: Dockerfile#L70
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#L74
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
i-am-bee~bee-ui~QC8UOU.dockerbuild
121 KB