Skip to content
PR

ORV2-1682 Display CorrelationId in Unexpected Error Page #5747

Sign in to view logs

ORV2-1682 Display CorrelationId in Unexpected Error Page

ORV2-1682 Display CorrelationId in Unexpected Error Page #5747

Triggered via pull request November 13, 2024 16:54
@krishnan-aotkrishnan-aot
synchronize #1665
erp2
Status Success
Total duration 2m 38s
Artifacts 1

pr-open.yml

on: pull_request
Set Variables
3s
Set Variables
PR Description Add
7s
PR Description Add
Matrix: Builds
Deploys (Dev)  /  ...  /  Helm
1m 46s
Deploys (Dev) / Deploys (DEV) / Helm
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
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/
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/
Deploys (Dev) / Deploys (DEV) / Helm
Multiple files were found for oc that matched the current OS and architecture: openshift-client-linux-4.17.4.tar.gz, openshift-client-linux-amd64-rhel8-4.17.4.tar.gz, openshift-client-linux-amd64-rhel9-4.17.4.tar.gz, openshift-client-linux-arm64-4.17.4.tar.gz, openshift-client-linux-arm64-rhel8-4.17.4.tar.gz, openshift-client-linux-arm64-rhel9-4.17.4.tar.gz, openshift-client-linux-ppc64le-4.17.4.tar.gz, openshift-client-linux-ppc64le-rhel8-4.17.4.tar.gz, openshift-client-linux-ppc64le-rhel9-4.17.4.tar.gz, openshift-client-linux-s390x-rhel8-4.17.4.tar.gz, openshift-client-linux-s390x-rhel9-4.17.4.tar.gz. Selecting the first one.

Artifacts

Produced during runtime
Name Size
bcgov~onroutebc~PQYG2N.dockerbuild
44.1 KB