Skip to content

Fix for add_tracking_entry in build.create_output (#8310) #7297

Fix for add_tracking_entry in build.create_output (#8310)

Fix for add_tracking_entry in build.create_output (#8310) #7297

Triggered via push October 18, 2024 00:41
Status Success
Total duration 3h 43m 7s
Artifacts 1

docker.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Legacy key/value format with whitespace separator should not be used: contrib/container/Dockerfile#L24
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: contrib/container/Dockerfile#L41
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "INVENTREE_SECRET_KEY_FILE") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Variables should be defined before their use: contrib/container/Dockerfile#L52
UndefinedVar: Usage of undefined variable '$DATE' (did you mean $PATH?) More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: contrib/container/Dockerfile#L142
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/
Legacy key/value format with whitespace separator should not be used: contrib/container/Dockerfile#L23
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
inventree~InvenTree~W6I2R9.dockerbuild
209 KB