Skip to content
Build App for Production

Merge pull request #60 from piny940/auth-logo #32

Sign in to view logs

Merge pull request #60 from piny940/auth-logo

Merge pull request #60 from piny940/auth-logo #32

Triggered via push November 4, 2024 08:15
@piny940piny940
pushed 3df823c
main
Status Success
Total duration 2m 14s
Artifacts 2

prd-deploy.yaml

on: push
filter
3s
filter
prd-build-backend
1m 2s
prd-build-backend
build-doc
0s
build-doc
prd-build-frontend
1m 52s
prd-build-frontend
prd-build-example
0s
prd-build-example
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Legacy key/value format with whitespace separator should not be used: frontend/Dockerfile#L10
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: frontend/Dockerfile#L11
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: frontend/Dockerfile#L31
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: frontend/Dockerfile#L38
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
piny940~auth~TCC905.dockerbuild
39.6 KB
piny940~auth~UHN0TC.dockerbuild
50.3 KB