Skip to content

ROCKS-30 Migration update cancel button #254

ROCKS-30 Migration update cancel button

ROCKS-30 Migration update cancel button #254

Triggered via push October 7, 2024 19:07
Status Success
Total duration 7m 39s
Artifacts 4
deploy  /  ...  /  Run unit tests
31s
deploy / Unit tests / Run unit tests
deploy  /  ...  /  Notify of Start
5s
deploy / Notify of Start / Notify of Start
deploy  /  ...  /  Build Image
26s
deploy / build-push-images / Build Image
deploy  /  ...  /  Trim Registry
15s
deploy / build-push-images / trim-registry-images / Trim Registry
deploy  /  ...  /  Update Docker Compose
10s
deploy / Update docker-compose / Update Docker Compose
deploy  /  ...  /  Run end-to-end tests
1m 42s
deploy / End-to-end tests / Run end-to-end tests
deploy  /  ...  /  Deploy New Image to Kubernetes Cluster
3m 37s
deploy / deploy-image-to-k8s / Deploy New Image to Kubernetes Cluster
deploy  /  ...  /  Notify of Conclusion
4s
deploy / Notify of Conclusion / Notify of Conclusion
Fit to window
Zoom out
Zoom in

Annotations

13 warnings
deploy / Unit tests / Run unit tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L3
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#L4
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#L9
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#L23
UndefinedVar: Usage of undefined variable '$VCS_REF' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
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#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/
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/
Variables should be defined before their use: Dockerfile#L23
UndefinedVar: Usage of undefined variable '$BUILD_DATE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
deploy / End-to-end tests / Run end-to-end tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
deploy / Notify of 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
239 Bytes
deployment-logs
11.1 KB
docker-compose
503 Bytes
unb-libraries~unbgeology.lib.unb.ca~OOS7Z2.dockerbuild
44.9 KB