Skip to content

fix: UI space problems #221

fix: UI space problems

fix: UI space problems #221

Triggered via push December 31, 2024 16:29
Status Success
Total duration 7m 59s
Artifacts 3

deploy.yml

on: push
Set Environment
0s
Set Environment
trigger_build
5s
trigger_build
Build Client image and push to Amazon ECR
2m 57s
Build Client image and push to Amazon ECR
Build API image and push to Amazon ECR
21s
Build API image and push to Amazon ECR
Build Backoffice image and push to Amazon ECR
1m 11s
Build Backoffice image and push to Amazon ECR
Deploy Services to Amazon EBS
4m 29s
Deploy Services to Amazon EBS
Fit to window
Zoom out
Zoom in

Annotations

34 warnings
Set Environment
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
trigger_build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Build API 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: api/Dockerfile#L12
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "EMAIL_CONFIRMATION_TOKEN_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: api/Dockerfile#L24
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: api/Dockerfile#L25
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: api/Dockerfile#L28
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "ACCESS_TOKEN_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: api/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/
Legacy key/value format with whitespace separator should not be used: api/Dockerfile#L34
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: api/Dockerfile#L34
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "ACCOUNT_CONFIRMATION_TOKEN_SECRET") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: api/Dockerfile#L7
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "DB_PASSWORD") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: api/Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "RESET_PASSWORD_TOKEN_SECRET") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Sensitive data should not be used in the ARG or ENV commands: api/Dockerfile#L13
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "EMAIL_CONFIRMATION_TOKEN_EXPIRES_IN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
Build Backoffice 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
Legacy key/value format with whitespace separator should not be used: backoffice/Dockerfile#L14
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: backoffice/Dockerfile#L15
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: backoffice/Dockerfile#L19
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: backoffice/Dockerfile#L10
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "BACKOFFICE_SESSION_COOKIE_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: backoffice/Dockerfile#L13
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: backoffice/Dockerfile#L16
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: backoffice/Dockerfile#L16
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "DB_PASSWORD") 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: backoffice/Dockerfile#L17
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: backoffice/Dockerfile#L18
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: backoffice/Dockerfile#L19
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ENV "BACKOFFICE_SESSION_COOKIE_SECRET") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/
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
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/
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/
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 Red and health status is Severe. Giving it 30 seconds to recover...
Deploy Services to Amazon EBS
Environment still has health: Yellow and health status Warning. Waiting 19 more seconds before failing...

Artifacts

Produced during runtime
Name Size
Vizzuality~tnc-blue-carbon-cost-tool~K7T37N.dockerbuild
55.4 KB
Vizzuality~tnc-blue-carbon-cost-tool~LFE670.dockerbuild
53.3 KB
Vizzuality~tnc-blue-carbon-cost-tool~UXLZ7C.dockerbuild
43 KB