Application Updates #201
deployment-workflow.yaml
on: pull_request
deploy
/
...
/
Build Image
1m 27s
deploy
/
...
/
Notify of Start
2s
deploy
/
...
/
Deploy New Image to Kubernetes Cluster
deploy
/
...
/
Check Deployment Logs for Errors
deploy
/
...
/
Notify of Conclusion
7s
Annotations
3 errors and 11 warnings
deploy / Build/Push Images / trim-registry-images / Trim Registry
Process completed with exit code 1.
|
deploy / Build/Push Images / trim-registry-images / Trim Registry
Unable to process file command 'output' successfully.
|
deploy / Build/Push Images / trim-registry-images / Trim Registry
Invalid format 'No matching tags found. Something likely went wrong.'
|
Legacy key/value format with whitespace separator should not be used:
Dockerfile#L6
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#L7
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#L8
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#L11
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#L5
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#L10
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:
Dockerfile#L33
UndefinedVar: Usage of undefined variable '$BUILD_DATE'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Variables should be defined before their use:
Dockerfile#L33
UndefinedVar: Usage of undefined variable '$VCS_REF'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
Variables should be defined before their use:
Dockerfile#L33
UndefinedVar: Usage of undefined variable '$VERSION'
More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
|
The MAINTAINER instruction is deprecated, use a label instead to define an image author:
Dockerfile#L2
MaintainerDeprecated: Maintainer instruction is deprecated in favor of using label
More info: https://docs.docker.com/go/dockerfile/rule/maintainer-deprecated/
|
deploy / Notify Conclusion / Notify of Conclusion
The following actions use a deprecated Node.js version and will be forced to run on node20: technote-space/workflow-conclusion-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
build-image-tag
Expired
|
241 Bytes |
|
unb-libraries~unbherbarium.lib.unb.ca~NIWKTI.dockerbuild
Expired
|
60.7 KB |
|