Skip to content
Bygg og deploy AAP Søknad

🥅 Bedre feilmelding for 422 respons på opplastede filer #94

Sign in to view logs

🥅 Bedre feilmelding for 422 respons på opplastede filer

🥅 Bedre feilmelding for 422 respons på opplastede filer #94

Triggered via push October 11, 2024 13:41
@tidnavtidnav
pushed 18b9b18
main
Status Success
Total duration 5m 42s
Artifacts 2

build-and-deploy.yaml

on: push
buildProd  /  build
3m 39s
buildProd / build
buildDev  /  build
3m 34s
buildDev / build
deployProd  /  deploy
1m 42s
deployProd / deploy
Deploy alerts to prod
10s
Deploy alerts to prod
deployDev  /  deploy
1m 30s
deployDev / deploy
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L16
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#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: Dockerfile#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: Dockerfile#L16
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
navikt~aap-soknad~SRJ0LY.dockerbuild
66.1 KB
navikt~aap-soknad~VIVE2O.dockerbuild
65.7 KB