Skip to content

🎨 bumps (#105)

🎨 bumps (#105) #31

Triggered via push August 19, 2026 11:35
Status Success
Total duration 2m 1s
Artifacts 1

PROD-web.yaml

on: push
deploy-production
1m 57s
deploy-production
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Legacy key/value format with whitespace separator should not be used: web/Dockerfile#L65
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: web/Dockerfile#L64
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: web/Dockerfile#L59
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: web/Dockerfile#L58
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: web/Dockerfile#L39
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: web/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 Digest
equinor~brandwalls~MMC9HD.dockerbuild
67.1 KB
sha256:b2539a37c4f877c0b2fc4e81ea7b07504ea79ad5dd0e5e2c937c1d37467de563