Skip to content
This repository was archived by the owner on Jun 14, 2024. It is now read-only.
This repository was archived by the owner on Jun 14, 2024. It is now read-only.

Plugin fails when using deep project structure #108

@swftvsn

Description

@swftvsn

I have a project that has layout like this:

 - root
   | - ios
   | - android
   | - handler (in google cloud)
   | - trigger (in google cloud)
   | - etc..

When I run ./gradlew handler:appengineStage from the root directory, staging fails with exception

Directory '[removed]/root/src/main/appengine' specified for property 'stagingConfig.appEngineDirectory' does not exist.

With plugin version 1.0 this used to work, but not anymore with 1.1. Should I have one appengine directory in the root folder and then separate appengine folders in handler and trigger folders?

All the projects are deployed to the same Google Cloud project, but represent different Services, so the cron.yaml should go to root/src/main/appengine, but the app.yaml files to project specific appengine folders? Is this correct? I have src/main/appengine folder in all projects that are destined to be deployed to Google Cloud, but not in the root project.

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions