Thanks for all your feedback on this change. We heard from many of you that, while the Jenkins-based solution we offer works <https://cloud.google.com/tools/repo/push-to-deploy>well for larger projects with dedicated build and test steps, it works much less well for more simple projects with no build or test steps.
To that end, we are going to continue to support push to deploy for existing projects that don’t require build or test. For example, python or php applications code be pushed to the git repo and will be deployed to app engine just as it works today. We continue to recommend jenkins <https://cloud.google.com/tools/repo/push-to-deploy>for applications that require build and test steps. If you have any problems with the source only deployments, please do let me know. Thanks again for your feedback. ..brad On Mon Feb 02 2015 at 12:57:30 PM Syrus Mesdaghi <syr...@gmail.com> wrote: > At the very least you should have a one liner notice when someone goes to > setup a new pipeline with deploy source only mentioning that it is > deprecated. We have a project that is still building as 'deploy source > only'... I made a new project and have spent days trying to figure out why > it doesn't deploy. I just happened to come across this thread in my > desperate attempts to figure out what is going on. I agree with Lucas that > "At least pushing source should remain as a feature". Having to do a lot > more to do exactly what we needed doesn't feel like an upgrade though I'm > sure some users will enjoy the extra capability. > > On Friday, December 19, 2014 at 6:44:30 PM UTC-5, Lucas Geiger wrote: >> >> Guys, this is absurd. You finally got the push-to-deploy product right , >> and now you are discontinuing it. At least pushing source should remain as >> a feature. >> The whole appeal of push to deploy was NOT setting up Jenkins. I think >> you are misjudging the number of people who object to using Jenkins. >> (By the way it was very disrespectful of you to cloak this >> discontinuation as a feature upgrade. A tasteless and disingenuous tactic, >> to be precise.) > > -- > 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 google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at http://groups.google.com/group/google-appengine. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-appengine/c668fa0a-6c6a-4a82-8a28-e3f1a4f4eb83%40googlegroups.com > <https://groups.google.com/d/msgid/google-appengine/c668fa0a-6c6a-4a82-8a28-e3f1a4f4eb83%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAHLXp%3DG1m6OWuYyq8TYfpYXKXbpkz_XCs1NFWnNQHCOvHGQ3pw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
