Skip to content
ci

fix: fixed docker build #6

Sign in to view logs

fix: fixed docker build

fix: fixed docker build #6

Triggered via push February 29, 2024 14:02
@marinoandreamarinoandrea
pushed 686b9f6
main
Status Failure
Total duration 2m 46s
Artifacts –

ci.yaml

on: push
build-api
1m 23s
build-api
build-app
1m 42s
build-app
deploy
47s
deploy
migrate
0s
migrate
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
deploy
google-github-actions/deploy-cloudrun failed with: failed to execute gcloud command `gcloud run deploy rimun-api --quiet --image eu.gcr.io/***/rimun-api:686b9f68d33e9138cc5d3d24a93568e5a55c0918 --update-env-vars SENTRY_DSN=***,PASSWORD_RECOVERY_URL=https://rimun.com/dashboard/password-recovery,DATABASE_URL=***,MAIL_HOST=46.252.150.104,MAIL_PORT=465,MAIL_USERNAME=***,MAIL_PASSWORD=***,FTP_HOST=46.252.150.104,FTP_USER=***,FTP_PASSWORD=***,JWT_SECRET=***,SECRET_KEY=***,MAIL_CONTACT_RECIPIENT=info@rimun.com --update-labels managed-by=github-actions,commit-sha=686b9f68d33e9138cc5d3d24a93568e5a55c0918 --platform managed --format json --region europe-west8`: Deploying container to Cloud Run service [rimun-api] in project [***] region [europe-west8] Deploying... Creating Revision..........................................................................................................................................................................................................................failed Deployment failed ERROR: (gcloud.run.deploy) Revision 'rimun-api-00023-rbt' is not ready and cannot serve traffic. The user-provided container failed to start and listen on the port defined provided by the PORT=3000 environment variable. Logs for this revision might contain more information. Logs URL: https://console.cloud.google.com/logs/viewer?project=***&resource=cloud_run_revision/service_name/rimun-api/revision_name/rimun-api-00023-rbt&advancedFilter=resource.type%3D%22cloud_run_revision%22%0Aresource.labels.service_name%3D%22rimun-api%22%0Aresource.labels.revision_name%3D%22rimun-api-00023-rbt%22 For more troubleshooting guidance, see https://cloud.google.com/run/docs/troubleshooting#container-failed-to-start
build-api
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, google-github-actions/auth@v1, google-github-actions/setup-gcloud@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-api
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-app
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, google-github-actions/auth@v1, google-github-actions/setup-gcloud@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-app
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
deploy
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: google-github-actions/auth@v1, google-github-actions/deploy-cloudrun@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
deploy
The "create_credentials_file" option is true, but the current GitHub workspace is empty. Did you forget to use "actions/checkout" before this step? If you do not intend to share authentication with future steps in this job, set "create_credentials_file" to false.