Hi Maxim, We currently don't deploy from our CI and also have a much simpler test scenario, but we are always thinking about integrating online tests and hence also a GAE deployment into our CI process. Here a few thoughts about this:
o We have dev, staging and production environments, each running as a separate app. o Clearing a datastore always affects a whole app, so running staging and prod as different versions of the same app is always risky and you'll end up working around potential issues. o We don't use namespaces (currently - but don't see any use for them, neither for multi tenancy nor for separating environments). Why do you need separate versions to run your tests? If you integrate all test scenarios on a single application, you can run them as different (HTTP-) Requests inside a single app version, either concurrently or sequentially, driven from your CI environment or from a single requests that starts multiple queued tasks. Running the test sequentially even allows to clear the datastore between tests etc. In any case, try not to overengineer it, keep it as simple as possible. I hope these thoughts may help you. Cheers, Remigius. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
