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. For more options, visit https://groups.google.com/d/optout.
