Back to pull request #1588

Fix cached application data bug #5335

Sign in to view logs

Triggered via pull request September 9, 2024 21:18

zgong-gov

opened #1588

application-cache-bug

Status Success

Total duration 4m 14s

Artifacts 1

pr-open.yml

on: pull_request

PR Description Add

Matrix: Builds

Annotations

6 warnings

The 'as' keyword should match the case of the 'from' keyword: frontend/Dockerfile#L42

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: frontend/Dockerfile#L14

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: frontend/Dockerfile#L15

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: frontend/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: frontend/Dockerfile#L17

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: frontend/Dockerfile#L18

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
bcgov~onroutebc~NJTNUH.dockerbuild	73 KB