Skip to content
develop-blockchains

Chia 2.5.5 @ rc7 #46

Sign in to view logs

Chia 2.5.5 @ rc7

Chia 2.5.5 @ rc7 #46

Triggered via push August 12, 2025 19:08
@guydavisguydavis
pushed 24ea730
develop
Status Success
Total duration 1h 13m 10s
Artifacts 2

develop-blockchains.yaml

on: push
chia
1h 7m
chia
gigahorse
1h 13m
gigahorse
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Legacy key/value format with whitespace separator should not be used: docker/dockerfile#L143
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/dockerfile#L142
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/dockerfile#L141
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/dockerfile#L132
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/dockerfile#L131
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/dockerfile#L143
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/dockerfile#L142
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/dockerfile#L141
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/dockerfile#L132
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/dockerfile#L131
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 Digest
guydavis~machinaris~I6UYWP.dockerbuild
129 KB
sha256:7222f3a0aeb3c3278c7f3954af29793330307d73f09a5a8c7ac8461eb6d5c1e1
guydavis~machinaris~KSJ8JW.dockerbuild
134 KB
sha256:bf8422e7e814ab11f9e38fa1ee74030fe6762e0b0daf98588462c0ce330475c0