What are your intentions with a feature branch? Like adding a new feature to production, hence deploying a new version? Or you want to launch an alternate modified service with an additional feature just for testing purposes.
GAE has the microservice concept as its core. I'd like to think you could exploit this to your advantage, for example, deploying the same code under two different service "versions", one of them being your feature branch. You could do traffic migration <https://cloud.google.com/appengine/docs/standard/python/splitting-traffic>, if it works for you. In fact, you can deploy a new version of your service and still ensure the traffic goes 100% to the old version. It is fair to say it really depends on your scenario and setup. What have you tried? Are you using development and production environments? If not, review this: - https://cloud.google.com/appengine/docs/standard/php/creating-separate-dev-environments - https://stackoverflow.com/questions/3793860/how-to-set-up-a-staging-environment-on-google-app-engine On Saturday, May 22, 2021 at 4:45:13 PM UTC-4 [email protected] wrote: > > Hello, > As part of implementing GitFlow in my project, I would like to know how > can I deploy a feature branch on Google App Engine so that QA can do the > testing on the feature branch? > > Thanks > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/5e2a8ecf-760d-4548-8b19-698fdc481d18n%40googlegroups.com.
