Skip to content
Bygg og deploy AAP Søknad

♻️ logInfo når bruker redirectes fra [step] til starten av søknad #118

Sign in to view logs

♻️ logInfo når bruker redirectes fra [step] til starten av søknad

♻️ logInfo når bruker redirectes fra [step] til starten av søknad #118

Triggered via push November 14, 2024 08:49
@tidnavtidnav
pushed 0cd18e0
main
Status Success
Total duration 7m 42s
Artifacts 2

build-and-deploy.yaml

on: push
buildProd  /  build
5m 8s
buildProd / build
buildDev  /  build
4m 18s
buildDev / build
Deploy alerts to prod
11s
Deploy alerts to prod
deployDev  /  deploy
1m 37s
deployDev / deploy
deployProd  /  deploy
1m 24s
deployProd / deploy
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
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#L12
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#L12
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~RF9G8D.dockerbuild
99.4 KB
navikt~aap-soknad~ST9V1B.dockerbuild
76 KB