App Engine Deployment Error

117 views
Skip to first unread message

Golden Andro

unread,
Aug 23, 2018, 8:59:04 AM8/23/18
to Google App Engine
Hi Everyone,

Good day.
I encountered an issue during app engine deployment, as follows:

> gradle :api:appengineDeploy --stacktrace --info

The error was:

[log]
...
:api:appengineDeploy (Thread[Task worker for ':' Thread 2,5,main]) completed. Took 0.005 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':api:appengineDeploy'.
> Cloud SDK versions before 145.0.0 are not supported

[/log]

I checked the gcloud version:

> gcloud version
Google Cloud SDK 201.0.0
alpha 2018.05.11
app-engine-go
app-engine-java 1.9.63
app-engine-python 1.9.67
beta 2018.05.11
bigtable
bq 2.0.33
cbt
cloud-datastore-emulator 1.4.1
core 2018.05.11
datalab 20180213
gsutil 4.31
pubsub-emulator 2018.03.23

I did try to update gcloud but I got this error:

> gcloud components update
[log]
ERROR: (gcloud.components.update) You cannot perform this action because this Cloud SDK installation is managed by an external package manager.
[/log]

The api build.gradle file contains:
[code]

  dependencies {
    classpath 'com.google.cloud.tools:appengine-gradle-plugin:1.3.3'
    classpath 'com.google.cloud.tools:endpoints-framework-gradle-plugin:1.0.0'
  }

[/code]

Has anyone encountered this issue? Thanks.

Regards,


David (Google Cloud Support)

unread,
Aug 23, 2018, 1:00:56 PM8/23/18
to Google App Engine

Hello,


I recommend you to update your Cloud SDK components as this deployment error might be due to using outdated components. I can see that you tried to do so  by running “gcloud components update” but please note that the Cloud SDK component manager only works if you don't install the SDK through another package manager Managing Cloud SDK Components. Please uninstall the Google Cloud SDK and reinstall using one of the installation options listed in this document Installing Google Cloud SDK.  


After reinstalling, your Google Cloud SDK should be up to date, the current version is 213.0.0. You should then try to perform the deployment again to see if this resolved the issue.
Reply all
Reply to author
Forward
0 new messages