Skip to content

project creation: ignores restoration years when creating conservatio… #196

project creation: ignores restoration years when creating conservatio…

project creation: ignores restoration years when creating conservatio… #196

Triggered via push December 18, 2024 16:50
Status Success
Total duration 6m 18s
Artifacts 1

deploy.yml

on: push
Set Environment
0s
Set Environment
trigger_build
3s
trigger_build
Build Client image and push to Amazon ECR
2m 40s
Build Client image and push to Amazon ECR
Build API image and push to Amazon ECR
0s
Build API image and push to Amazon ECR
Build Backoffice image and push to Amazon ECR
0s
Build Backoffice image and push to Amazon ECR
Deploy Services to Amazon EBS
3m 6s
Deploy Services to Amazon EBS
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
trigger_build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Set Environment
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build Client image and push to Amazon ECR
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
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/
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/
Deploy Services to Amazon EBS
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Deploy Services to Amazon EBS
Environment update finished, but health is Yellow and health status is Warning. Giving it 30 seconds to recover...

Artifacts

Produced during runtime
Name Size
Vizzuality~tnc-blue-carbon-cost-tool~BZ0OCR.dockerbuild
55.3 KB