Resolving Linting Issues For Scheduler #5538
pr-open.yml
on: pull_request
Set Variables
3s
PR Description Add
8s
Matrix: Builds
Deploys (Dev)
/
...
/
Helm
1m 45s
Annotations
11 warnings
Legacy key/value format with whitespace separator should not be used:
scheduler/Dockerfile#L31
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:
scheduler/Dockerfile#L37
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:
scheduler/Dockerfile#L40
UndefinedVar: Usage of undefined variable '$MSSQL_DB'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Legacy key/value format with whitespace separator should not be used:
scheduler/Dockerfile#L42
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:
scheduler/Dockerfile#L57
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:
scheduler/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:
scheduler/Dockerfile#L52
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:
scheduler/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:
scheduler/Dockerfile#L58
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:
scheduler/Dockerfile#L47
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.0.tar.gz, openshift-client-linux-amd64-rhel8-4.17.0.tar.gz, openshift-client-linux-amd64-rhel9-4.17.0.tar.gz, openshift-client-linux-arm64-4.17.0.tar.gz, openshift-client-linux-arm64-rhel8-4.17.0.tar.gz, openshift-client-linux-arm64-rhel9-4.17.0.tar.gz, openshift-client-linux-ppc64le-4.17.0.tar.gz, openshift-client-linux-ppc64le-rhel8-4.17.0.tar.gz, openshift-client-linux-ppc64le-rhel9-4.17.0.tar.gz, openshift-client-linux-s390x-rhel8-4.17.0.tar.gz, openshift-client-linux-s390x-rhel9-4.17.0.tar.gz. Selecting the first one.
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
bcgov~onroutebc~M4XAKQ.dockerbuild
|
57.2 KB |
|