Skip to content

cant use progress bar on alpine base #174

cant use progress bar on alpine base

cant use progress bar on alpine base #174

Triggered via push November 13, 2024 02:48
Status Success
Total duration 9m 38s
Billable time 4m
Artifacts 8

publish.yml

on: push
lint_test  /  build
0s
lint_test / build
lint_test  /  lint
1m 17s
lint_test / lint
lint_test  /  unit-tests
4m 36s
lint_test / unit-tests
lint_test  /  integration-tests
0s
lint_test / integration-tests
lint_test  /  check-mock-gen
0s
lint_test / check-mock-gen
lint_test  /  gosec
0s
lint_test / gosec
docker_pipeline  /  prepare-metadata
0s
docker_pipeline / prepare-metadata
docker_pipeline  /  dockerfile_lint
18s
docker_pipeline / dockerfile_lint
Matrix: docker_pipeline / docker_build
docker_pipeline  /  merge_dockerhub
9s
docker_pipeline / merge_dockerhub
docker_pipeline  /  merge_ecr
18s
docker_pipeline / merge_ecr
docker_pipeline  /  vulnerability_scan
31s
docker_pipeline / vulnerability_scan
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
docker_pipeline / dockerfile_lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
docker_pipeline / vulnerability_scan
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
babylonlabs-io~babylon~1CQ7YE.dockerbuild
27.3 KB
babylonlabs-io~babylon~KEBODK.dockerbuild
49.5 KB
babylonlabs-io~babylon~UOPFBT.dockerbuild
27.2 KB
babylonlabs-io~babylon~XZRLC7.dockerbuild
50.7 KB
digests-dockerhub-linux-amd64 Expired
303 Bytes
digests-dockerhub-linux-arm64 Expired
303 Bytes
digests-ecr-linux-amd64 Expired
303 Bytes
digests-ecr-linux-arm64 Expired
303 Bytes