Skip to content
Build and deploy

feat: use back instead of file for mfs #27

Sign in to view logs

feat: use back instead of file for mfs

feat: use back instead of file for mfs #27

Triggered via push November 25, 2024 14:11
@JoeSlainJoeSlain
pushed a3cb831
dev
Status Success
Total duration 1m 44s
Artifacts 1

build_and_deploy.yml

on: push
Build and push from dev/a3cb831cc888386654cf64e55e9dc7f19dceb23a
1m 24s
Build and push from dev/a3cb831cc888386654cf64e55e9dc7f19dceb23a
Deploy from dev/a3cb831cc888386654cf64e55e9dc7f19dceb23a
2s
Deploy from dev/a3cb831cc888386654cf64e55e9dc7f19dceb23a
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#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: Dockerfile#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/
Legacy key/value format with whitespace separator should not be used: Dockerfile#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: Dockerfile#L8
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: Dockerfile#L9
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/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile#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/

Artifacts

Produced during runtime
Name Size
etalab-ia~franceservices-frontend~IGWBLW.dockerbuild
66.2 KB