Skip to content
develop-blockchains

Gigahorse @ 2.5.5.giga36 #48

Sign in to view logs

Gigahorse @ 2.5.5.giga36

Gigahorse @ 2.5.5.giga36 #48

Re-run triggered August 27, 2025 02:55
@guydavisguydavis
ab09086
develop
Status Success
Total duration 1h 14m 25s
Artifacts 2

develop-blockchains.yaml

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

Annotations

5 warnings
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/

Artifacts

Produced during runtime
Name Size Digest
guydavis~machinaris~S7VS6S.dockerbuild
139 KB
sha256:f17c5b5743d89beca92e7a46ac7fadc20e6df424bbbb4c39168f1772ba1d37f6