Skip to content
Deploy

Trio (#730) #54

Sign in to view logs

Trio (#730)

Trio (#730) #54

Triggered via push November 26, 2024 21:17
@github-merge-queuegithub-merge-queue[bot]
pushed b98043b
main
Status Success
Total duration 1m 45s
Artifacts 1

deploy.yml

on: push
Docker
1m 2s
Docker
Deploy
27s
Deploy
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
Legacy key/value format with whitespace separator should not be used: Dockerfile#L98
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/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L22
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L79
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#L80
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#L81
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#L97
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
beam-community~elixir-companies~R34GBP.dockerbuild
64.7 KB