Skip to content
build-push-release-images

🍕 Update auto-generate ssl scripts to regenerate #7

Sign in to view logs

🍕 Update auto-generate ssl scripts to regenerate

🍕 Update auto-generate ssl scripts to regenerate #7

Triggered via push November 17, 2024 15:04
@ffimnsrffimnsr
pushed 8857c7e
release-1.0.10
Status Success
Total duration 1m 26s
Artifacts 1

build-push-release-images.yml

on: push
build
1m 15s
build
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Legacy key/value format with whitespace separator should not be used: Containerfile#L7
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: Containerfile#L3
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: Containerfile#L4
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: Containerfile#L5
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: Containerfile#L6
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 Digest
ffimnsr~jmail~UM7UEK.dockerbuild Expired
81.9 KB
sha256:e9abf039df94871e5a3716ea9b28c61a23a98b039d21a7b69427e13434ee69a8