Skip to content

Fix slashing tooltip (#613) #352

Fix slashing tooltip (#613)

Fix slashing tooltip (#613) #352

Triggered via push January 14, 2025 18:08
Status Success
Total duration 7m 25s
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~4XCPO5.dockerbuild
42.7 KB
babylonlabs-io~simple-staking~8BSJXL.dockerbuild
42.1 KB
babylonlabs-io~simple-staking~CJBYEC.dockerbuild
41.4 KB
babylonlabs-io~simple-staking~G45KI5.dockerbuild
42 KB
babylonlabs-io~simple-staking~GC7PWI.dockerbuild
42.2 KB
babylonlabs-io~simple-staking~OVM7X7.dockerbuild
42.3 KB
babylonlabs-io~simple-staking~TI9507.dockerbuild
41.7 KB
simple-staking-devnet
89.7 MB
simple-staking-mainnet
89.7 MB
simple-staking-mainnet-private
89.7 MB
simple-staking-phase-2-devnet
89.7 MB
simple-staking-phase-2-testnet
89.7 MB
simple-staking-staging
89.7 MB
simple-staking-testnet
89.7 MB