Skip to content

[TBCCT-123] Implemented ‘My Projects’ Page with Active Page Highlight… #97

[TBCCT-123] Implemented ‘My Projects’ Page with Active Page Highlight…

[TBCCT-123] Implemented ‘My Projects’ Page with Active Page Highlight… #97

Triggered via push November 14, 2024 12:53
Status Success
Total duration 6m 14s
Artifacts 1

deploy.yml

on: push
Set Environment
0s
Set Environment
Build Client image and push to Amazon ECR
2m 48s
Build Client image and push to Amazon ECR
Build API image and push to Amazon ECR
11s
Build API image and push to Amazon ECR
Build Admin image and push to Amazon ECR
12s
Build Admin image and push to Amazon ECR
Deploy Services to Amazon EBS
2m 56s
Deploy Services to Amazon EBS
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Legacy key/value format with whitespace separator should not be used: client/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/
Sensitive data should not be used in the ARG or ENV commands: client/Dockerfile#L4
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "NEXTAUTH_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: client/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: client/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/
Sensitive data should not be used in the ARG or ENV commands: client/Dockerfile#L9
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "NEXTAUTH_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: client/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/
Deploy Services to Amazon EBS
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@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
Vizzuality~tnc-blue-carbon-cost-tool~UJR1DB.dockerbuild
57.4 KB