Skip to content
image-build-test

Add TCP connection support for OVS #128

Sign in to view logs

Add TCP connection support for OVS

Add TCP connection support for OVS #128

Triggered via pull request November 12, 2024 13:47
@tabuhariritabuhariri
synchronize #330
tabuhariri:ovs_tcp_conn_pr
Status Success
Total duration 3m 51s
Artifacts 1

image-build-test.yaml

on: pull_request
build-image
3m 40s
build-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~I3ER7A.dockerbuild Expired
456 KB