Thank you, but I'm not sure how to achieve this. I selected the project 
with my standard environment app in gcloud init and tried to deploy the 
flex version using appengine:deploy and the appengine-maven-plugin. This 
worked a few weeks ago with a new project, although it took about 15mins. 
This time, I waited for more than 30mins, then got the following failure:   

[INFO] GCLOUD: Beginning deployment of service [default]...
[INFO] GCLOUD: WARNING: Deployment of App Engine Flexible Environment apps 
is currently in Beta
[INFO] GCLOUD: Building and pushing image for service [default]
[INFO] GCLOUD: WARNING: No configuration information provided by runtime 
[java].ß

---- after about 30mins ---

INFO] GCLOUD: ERROR: (gcloud.app.deploy) ('The read operation timed out',)
[INFO] GCLOUD: This may be due to network connectivity issues. Please check 
your network settings, and the status of the service you are trying to 
reach.

----

I don't see any notifications in my project's activity log. What am I doing 
wrong? Could the (deprecated) <vm>true</vm> in my appengine-web.xml be the 
reason? Is there a possibility to set the log level of 
appengine-maven-plugin / gcloud under the hood to see more log output?

The other option you mentioned involved renaming the project. But how is 
this changing anything? The project-id cannot be changed and the project 
name is only an alias. So after changing the project name, deploying the 
flex app and revert the project name - how should that be different to my 
first approach?

Thank you!



Am Montag, 28. November 2016 22:35:46 UTC+1 schrieb George (Cloud Platform 
Support):
>
> If you don’t absolutely need the same app name with a different version to 
> run in the new environment, there is the option to rename your new app and 
> dedicate a new service to it, for the new environment, all under the same 
> project. As a result, your old app would continue running in the standard 
> environment, whereas the new one, freshly re-baptised, runs in the flex 
> environment, offering a new service. You would finally run 2 services 
> accepting traffic, and that should take care of their “friendly 
> coexistence”. 
>
> Still, both apps must exist within the same project, to access the same 
> Datastore, as the project ID secures common access. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/cd6f2fa8-7b5d-4c18-950e-6e93954c6789%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • [google-appengine]... Thomas Baldauf
    • [google-appen... 'George (Cloud Platform Support)' via Google App Engine
      • [google-a... Thomas Baldauf
        • [goog... 'George (Cloud Platform Support)' via Google App Engine
          • [... Thomas Baldauf
          • [... Thomas Baldauf
            • ... 'George (Cloud Platform Support)' via Google App Engine
              • ... Thomas Baldauf
                • ... 'George (Cloud Platform Support)' via Google App Engine
                • ... Thomas Baldauf
                • ... Thomas Baldauf
                • ... 'George (Cloud Platform Support)' via Google App Engine
                • ... Thomas Baldauf
                • ... 'George (Cloud Platform Support)' via Google App Engine
                • ... Thomas Baldauf

Reply via email to