Skip to content
build and publish release image

v0.0.21 #23

Sign in to view logs

v0.0.21

v0.0.21 #23

Triggered via release December 19, 2024 21:33
@matoushavlenamatoushavlena
released v0.0.21
Status Success
Total duration 1h 4m 14s
Artifacts 1

publish-release-image.yml

on: release
build-and-push
1h 4m
build-and-push
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
build-and-push
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L77
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/
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#L51
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#L73
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
i-am-bee~bee-ui~YOFKKC.dockerbuild
149 KB