Skip to content
Build App for Production

Merge pull request #206 from piny940/eslint9 #147

Sign in to view logs

Merge pull request #206 from piny940/eslint9

Merge pull request #206 from piny940/eslint9 #147

Triggered via push January 14, 2025 03:18
@piny940piny940
pushed dc9da89
main
Status Success
Total duration 3m 17s
Artifacts 3

prd-deploy.yaml

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

Annotations

9 warnings
filter
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
prd-build-backend
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: example/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: example/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: example/Dockerfile#L36
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#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~52AIV9.dockerbuild
58.4 KB
piny940~auth~IA31HZ.dockerbuild
44.2 KB
piny940~auth~TH29WM.dockerbuild
62 KB