Skip to content

phase 1 fp name (#633) #356

phase 1 fp name (#633)

phase 1 fp name (#633) #356

Triggered via push January 16, 2025 11:22
Status Success
Total duration 8m 3s
Artifacts 14

publish.yaml

on: push
Matrix: docker_build
Matrix: dockerhub_publish
Matrix: ecr_publish
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Legacy key/value format with whitespace separator should not be used: docker/Dockerfile#L61
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#L61
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#L61
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#L61
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#L61
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#L61
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#L61
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
babylonlabs-io~simple-staking~3R5PEA.dockerbuild
42.1 KB
babylonlabs-io~simple-staking~BVQ41P.dockerbuild
42.7 KB
babylonlabs-io~simple-staking~GYAFI6.dockerbuild
41.5 KB
babylonlabs-io~simple-staking~UV0V75.dockerbuild
42.4 KB
babylonlabs-io~simple-staking~X0DJ60.dockerbuild
42.5 KB
babylonlabs-io~simple-staking~YGW87V.dockerbuild
42.2 KB
babylonlabs-io~simple-staking~ZAOKGY.dockerbuild
42 KB
simple-staking-devnet
89.7 MB
simple-staking-mainnet
89.7 MB
simple-staking-mainnet-private
89.6 MB
simple-staking-phase-2-devnet
89.6 MB
simple-staking-phase-2-testnet
89.7 MB
simple-staking-staging
89.6 MB
simple-staking-testnet
89.7 MB