Skip to content
Test

Simple PR to check if DCO required #106

Sign in to view logs

Simple PR to check if DCO required

Simple PR to check if DCO required #106

Triggered via pull request January 2, 2025 04:33
@jafingerhutjafingerhut
opened #133
jafingerhut:check-if-dco-required
Status Success
Total duration 1m 44s
Artifacts 2

test.yml

on: pull_request
test
1m 34s
test
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
test
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.dev#L8
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/
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#L27
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#L28
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
p4lang~p4runtime-shell~NTI9XV.dockerbuild
53.5 KB
p4lang~p4runtime-shell~X0QV6L.dockerbuild
31.9 KB