Test #42
Annotations
1 error and 6 warnings
|
failed to execute gcloud command `gcloud beta run deploy sepomex-staging --image us-central1-docker.pkg.dev/sepomex-365521/icalialabs-sepomex/sepomex@sha256:e7f42db2e8da627d9512a08502f085d0c25f095c1dacc4b32a238514e51fe0d7 --quiet --platform managed --region us-central1 --update-env-vars DATABASE_URL=postgres://%2Fcloudsql%2Fsepomex-365521%3Aus-central1%3Asepomex/sepomex_staging,GOOGLE_CLOUD_PROJECT=sepomex-365521,DEPLOY_NAME=staging --update-secrets DATABASE_USERNAME=database-username:latest,DATABASE_PASSWORD=database-password:latest --revision-suffix 33f4c29-1692915701 --allow-unauthenticated --add-cloudsql-instances sepomex-365521:us-central1:sepomex --min-instances 0 --service-account [email protected] --project sepomex-365521 --format json`: Deploying container to Cloud Run service [sepomex-staging] in project [sepomex-365521] region [us-central1]
Deploying...
Setting IAM Policy...........done
Creating Revision.........done
Routing traffic....................................................................................................................................................................................................................failed
Deployment failed
ERROR: (gcloud.beta.run.deploy) Revision 'sepomex-staging-33f4c29-1692915701' is not ready and cannot serve traffic. The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable. Logs for this revision might contain more information.
Logs URL: https://console.cloud.google.com/logs/viewer?project=sepomex-365521&resource=cloud_run_revision/service_name/sepomex-staging/revision_name/sepomex-staging-33f4c29-1692915701&advancedFilter=resource.type%3D%22cloud_run_revision%22%0Aresource.labels.service_name%3D%22sepomex-staging%22%0Aresource.labels.revision_name%3D%22sepomex-staging-33f4c29-1692915701%22
For more troubleshooting guidance, see https://cloud.google.com/run/docs/troubleshooting#container-failed-to-start
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
The logs for this run have expired and are no longer available.
Loading