Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

Failure when using non-default named yaml file #316

Closed
gjferrier opened this issue Jun 22, 2018 · 1 comment
Closed

Failure when using non-default named yaml file #316

gjferrier opened this issue Jun 22, 2018 · 1 comment

Comments

@gjferrier
Copy link

Hi,

I've ran into a problem where specifying a non-default yaml file, e.g. mynew-app.yaml, the deployment fails. Here's the console output for the failed attempt

INFO: submitting command: /usr/lib/google-cloud-sdk/bin/gcloud app deploy /var/lib/jenkins/workspace/test-deploy/src/main/appengine/test-deploy-app.yaml

The deploy fails with

[INFO] GCLOUD: ERROR: (gcloud.app.deploy) Your application does not satisfy all of the requirements for a runtime of type [java]. Please correct the errors and try again.

However, if I use the same file, but use the default name 'app.yaml' the deployment works fine.

I am using version 1.3.1.

@chanseokoh
Copy link
Contributor

Dup of GoogleCloudPlatform/appengine-plugins#992. (However, the info in GoogleCloudPlatform/appengine-plugins#992 may be out of date.) Closing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants