Skip to content
Build App for Production

Merge pull request #127 from piny940/renovate/eslint-config-love-109.x #74

Sign in to view logs

Merge pull request #127 from piny940/renovate/eslint-config-love-109.x

Merge pull request #127 from piny940/renovate/eslint-config-love-109.x #74

Triggered via push November 30, 2024 11:34
@piny940piny940
pushed d67f189
main
Status Success
Total duration 2m 56s
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
2m 37s
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~V3G9SV.dockerbuild
54.6 KB
piny940~auth~WJHR9F.dockerbuild
44.1 KB