Skip to content

pull e2e ovs-cni fix: install latest ginkgo (#334) #16

pull e2e ovs-cni fix: install latest ginkgo (#334)

pull e2e ovs-cni fix: install latest ginkgo (#334) #16

Triggered via push November 12, 2024 11:30
Status Success
Total duration 4m 29s
Artifacts 1
build-and-push-image
4m 18s
build-and-push-image
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
The 'as' keyword should match the case of the 'from' keyword: cmd/Dockerfile#L1
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: cmd/Dockerfile#L15
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: cmd/Dockerfile#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: cmd/Dockerfile#L23
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: cmd/Dockerfile#L24
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
k8snetworkplumbingwg~ovs-cni~L60ZT0.dockerbuild
537 KB