Skip to content

refactor

refactor #2989

Triggered via push January 14, 2025 11:35
Status Success
Total duration 4m 51s
Artifacts 1

deploy-dev.yml

on: push
call-workflow  /  deploy-dev
4m 41s
call-workflow / deploy-dev
call-workflow  /  ...  /  CodeQL Analyze
1m 25s
call-workflow / CodeQL / CodeQL Analyze
Deploy redis
9s
Deploy redis
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Deploy redis
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
call-workflow / CodeQL / CodeQL Analyze
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: 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#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#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
navikt~pam-stillingsok~59HXUY.dockerbuild
78.4 KB