Skip to content

Fix/loadtests9

Fix/loadtests9 #5760

Triggered via pull request November 14, 2024 02:50
Status Cancelled
Total duration 2m 55s
Artifacts 3

pr-open.yml

on: pull_request
Set Variables
6s
Set Variables
PR Description Add
2s
PR Description Add
Matrix: Builds
Deploys (Dev)  /  ...  /  Helm
6s
Deploys (Dev) / Deploys (DEV) / Helm
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 27 warnings
Deploys (Dev) / Deploys (DEV) / Helm
Canceling since a higher priority waiting request for '1583' exists
Deploys (Dev) / Deploys (DEV) / Helm
The operation was canceled.
Legacy key/value format with whitespace separator should not be used: dops/Dockerfile#L43
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: dops/Dockerfile#L54
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: dops/Dockerfile#L61
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/
Sensitive data should not be used in the ARG or ENV commands: dops/Dockerfile#L64
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "CDOGS_CLIENT_SECRET") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Legacy key/value format with whitespace separator should not be used: dops/Dockerfile#L66
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: dops/Dockerfile#L67
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: dops/Dockerfile#L39
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/
Variables should be defined before their use: dops/Dockerfile#L45
UndefinedVar: Usage of undefined variable '$MSSQL_SA_USER' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: dops/Dockerfile#L45
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: dops/Dockerfile#L55
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: vehicles/Dockerfile#L35
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: vehicles/Dockerfile#L48
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/
Variables should be defined before their use: vehicles/Dockerfile#L53
UndefinedVar: Usage of undefined variable '$GL_CODE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Variables should be defined before their use: vehicles/Dockerfile#L58
UndefinedVar: Usage of undefined variable '$CFS_CREDIT_ACCOUNT_CLIENT_ID' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Variables should be defined before their use: vehicles/Dockerfile#L35
UndefinedVar: Usage of undefined variable '$VEHICLES_API_LOG_LEVEL' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: vehicles/Dockerfile#L41
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: vehicles/Dockerfile#L55
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/
Variables should be defined before their use: vehicles/Dockerfile#L57
UndefinedVar: Usage of undefined variable '$CFS_CREDIT_ACCOUNT_URL' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Variables should be defined before their use: vehicles/Dockerfile#L43
UndefinedVar: Usage of undefined variable '$MSSQL_ENCRYPT' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: vehicles/Dockerfile#L45
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/
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/
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~1C78GX.dockerbuild
65.9 KB
bcgov~onroutebc~OGNGE1.dockerbuild
48.3 KB
bcgov~onroutebc~VFO7Q8.dockerbuild
59.4 KB