Skip to content

chore(kustomize): add enable-helm flag for kustomize4 #807

chore(kustomize): add enable-helm flag for kustomize4

chore(kustomize): add enable-helm flag for kustomize4 #807

Triggered via pull request October 29, 2024 18:04
Status Success
Total duration 13m 13s
Artifacts 5

pr.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile.slim#L20
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.slim#L20
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.ubuntu#L19
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.java11.ubuntu#L19
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.java11.slim#L20
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
spinnaker~rosco~26YTQO.dockerbuild
95.6 KB
spinnaker~rosco~4SPVDP.dockerbuild
93 KB
spinnaker~rosco~D3Y0TB.dockerbuild
24.5 KB
spinnaker~rosco~I2GVS4.dockerbuild
429 KB
spinnaker~rosco~WB39WT.dockerbuild
411 KB