Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Suddenly unable to deploy since yesterday. [AppEngine]

Thanks for looking at my problem!

The following error occurs when executing the release command.
Please let me know the possibility of solving this problem.

 

╔════════════════════════════════════════════════════════════╗
╠═ Uploading 4 files to Google Cloud Storage                ═╣
╚════════════════════════════════════════════════════════════╝
File upload done.
Updating service [default]...failed.                                          
ERROR: (gcloud.app.deploy) Error Response: [13] An internal error occurred.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! xxxxxxxx@1.0.0 deploy: `NODE_ENV=development nuxt-ts build && gcloud app deploy app.yaml --project=xxxxxxxxxx`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the xxxxxxxxxx@1.0.0 deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/xxxxxxxxxx/.npm/_logs/2023-04-28T17_26_59_570Z-debug.log

 

Here is a more detailed situation.

1. The last successful deploy was on 4/25 (3 days ago).

2. we tried to deploy with multiple collaborators and terminals, but all returned the same error. In other words, it is highly possible that it is not even due to an individual terminal. 

3. deployed with the exact same source file as the one released on 25th. In other words, there is a high possibility that the problem is not caused by the source file.

4.The runtime used is nodejs14.

5. this is a web app made with Nuxt2.

6. i did some research on No.13 and tried a few things that might be the cause, but i couldn't figure it out for sure.

Hope you have a clue!

Solved Solved
0 1 308
1 ACCEPTED SOLUTION

I have discovered the cause of this problem.

https://cloud.google.com/appengine/docs/standard/nodejs/release-notes#April_11_2023

It seems to have been caused by an update to NodeRuntime that was also reflected in my app. I put the following code in package.json and it worked.

"scripts": {
  ...
  ,"gcp-build": ""
  ...
}

View solution in original post

1 REPLY 1

I have discovered the cause of this problem.

https://cloud.google.com/appengine/docs/standard/nodejs/release-notes#April_11_2023

It seems to have been caused by an update to NodeRuntime that was also reflected in my app. I put the following code in package.json and it worked.

"scripts": {
  ...
  ,"gcp-build": ""
  ...
}