Skip to content

[Humble] Use same Docker CI actions as main #1673

[Humble] Use same Docker CI actions as main

[Humble] Use same Docker CI actions as main #1673

Triggered via pull request November 15, 2024 13:03
Status Success
Total duration 2h 10m 11s
Artifacts 2

docker.yaml

on: pull_request
Matrix: ci
Matrix: release
Matrix: source
delete_untagged
2s
delete_untagged
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Legacy key/value format with whitespace separator should not be used: .docker/ci/Dockerfile#L6
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL 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: .docker/ci/Dockerfile#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: .docker/ci/Dockerfile#L10
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: .docker/release/Dockerfile#L6
LegacyKeyValueFormat: "LABEL key=value" should be used instead of legacy "LABEL 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: .docker/release/Dockerfile#L9
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
moveit~moveit2~WW28YQ.dockerbuild
124 KB
moveit~moveit2~XIERAH.dockerbuild
139 KB