Skip to content
Account Data Deleter

chore(ci): move to GitHub actions #3

Sign in to view logs

chore(ci): move to GitHub actions

chore(ci): move to GitHub actions #3

Triggered via pull request August 15, 2024 20:22
@bassrockbassrock
synchronize #678
github-actions
Status Failure
Total duration 4m 10s
Artifacts 1

account-data-deleter.yml

on: pull_request
test-integrations  /  main
3m 18s
test-integrations / main
infrastructure  /  plan
27s
infrastructure / plan
infrastructure  /  apply
0s
infrastructure / apply
build-and-push-image  /  pull-request
2m 8s
build-and-push-image / pull-request
build-and-push-image  /  development
0s
build-and-push-image / development
build-and-push-image  /  production
0s
build-and-push-image / production
build-and-push-lambda-events  /  pull-request
56s
build-and-push-lambda-events / pull-request
build-and-push-lambda-events  /  development
0s
build-and-push-lambda-events / development
build-and-push-lambda-events  /  production
0s
build-and-push-lambda-events / production
build-and-push-lambda-batch-delete  /  pull-request
57s
build-and-push-lambda-batch-delete / pull-request
build-and-push-lambda-batch-delete  /  development
0s
build-and-push-lambda-batch-delete / development
build-and-push-lambda-batch-delete  /  production
0s
build-and-push-lambda-batch-delete / production
Fit to window
Zoom out
Zoom in

Annotations

1 error and 7 warnings
infrastructure / plan
Process completed with exit code 1.
infrastructure / plan
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
infrastructure / plan
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile#L14
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SENTRY_AUTH_TOKEN") 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: Dockerfile#L39
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SENTRY_AUTH_TOKEN") 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: Dockerfile#L63
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SENTRY_AUTH_TOKEN") 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: Dockerfile#L121
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/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L126
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/

Artifacts

Produced during runtime
Name Size
Pocket~pocket-monorepo~MF6YZ4.dockerbuild Expired
37.1 KB