Skip to content
Continuous Integration

chore: improve time and distance formatting #90 #1763

Sign in to view logs

chore: improve time and distance formatting #90

chore: improve time and distance formatting #90 #1763

Triggered via push February 5, 2025 15:17
@frodrigofrodrigo
pushed 90d183f
develop
Status Success
Total duration 7m 8s
Artifacts 1

ci.yml

on: push
Matrix: Install code and deps
Matrix: Cypress
Matrix: Lint code base
docker
3m 25s
docker
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Default value for global ARG results in an empty or invalid base image name: Dockerfile#L2
InvalidDefaultArgInFrom: Default value for ARG node:${NODE_VERSION} results in empty or invalid base image name More info: https://docs.docker.com/go/dockerfile/rule/invalid-default-arg-in-from/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L16
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: Dockerfile#L22
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: Dockerfile#L23
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: Dockerfile#L24
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
teritorio~vido~DDQ6PP.dockerbuild
55.5 KB