I have also raised this question on Stackoverflow ( https://stackoverflow.com/questions/79583783/deploy-via-maven-to-gcp-standard-edition-has-started-to... ) and raised an issue on the GoogleCloudPlatformBuilders repo ( https://github.com/GoogleCloudPlatform/cloud-builders/issues/1056 ). I'm raising here too as I'm not sure whether those are the best places to ask my question
I have been using the following cloudbuild.yaml file for a number of years and it has worked perfectly.
steps:
- name: "gcr.io/cloud-builders/mvn:appengine"
args: ["-D", "skipTests", "-D", "endpoints.project.id=$_ENDPOINTS_PROJECT_ID", "-D", "app.deploy.projectId=$_PROJECT_NAME","clean", "package", "appengine:deploy", "-P", "$_PROFILE"]
timeout: "1600s"
Since last Tuesday / Wednesday ( 15th April 2025 ) if has started to fail, with this message.
Apr 15, 2025 10:52:36 AM com.google.cloud.tools.managedcloudsdk.install.Downloader download
INFO: Downloading https://dl.google.com/dl/cloudsdk/channels/rapid/google-cloud-sdk.tar.gz to /root/.cache/google-cloud-tools-java/managed-cloud-sdk/downloads/google-cloud-sdk.tar.gz
Welcome to the Google Cloud CLI!
WARNING: You appear to be running this script as root. This may cause
the installation to be inaccessible to users other than the root user.
/root/.cache/google-cloud-tools-java/managed-cloud-sdk/LATEST/google-cloud-sdk/install.sh: line 216: python: command not found
I have changed nothing in the build process, so I assume the CLI release around this time is the root of the problem, but I can't work out what I should do now. I don't see any documentation ( or none that I understand anyway ) that tells me what my next steps should be.
Any help greatly appreciated
LinkedIn
Twitter
