Skip to content

CI

CI #482

Triggered via schedule March 5, 2025 03:19
Status Success
Total duration 2m 8s
Artifacts 6

buildx.yml

on: schedule
check_paths  /  check_paths
3s
check_paths / check_paths
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
check_paths / check_paths
'before' field is missing in event payload - changes will be detected from last commit
build (linux/amd64): Dockerfile#L7
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/
build (linux/amd64): 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/
build (linux/arm64): 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/
build (linux/arm64): Dockerfile#L7
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/
build (linux/arm/v7): Dockerfile#L7
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/
build (linux/arm/v7): 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/

Artifacts

Produced during runtime
Name Size
JakobLichterfeld~TeslaMate-Telegram-Bot~ABDTUM.dockerbuild
43.5 KB
JakobLichterfeld~TeslaMate-Telegram-Bot~TD61JB.dockerbuild
45.9 KB
JakobLichterfeld~TeslaMate-Telegram-Bot~Z9WZTK.dockerbuild
47.1 KB
digests-linux-amd64 Expired
244 Bytes
digests-linux-arm-v7 Expired
244 Bytes
digests-linux-arm64 Expired
244 Bytes