I believe they sent emails to those that have used the service. Here's the contents:
Hello, The ability to quickly, easily and safely deploy your code is an important part of a great cloud developer experience. You have used the Release Pipelines feature on GCP to push-to-deploy and have given us very insightful feedback. We heard clearly that you want more flexibility and control. So we have decided to move the product in this direction. Instead of a pipeline with a small number of options, we want to offer you the full flexibility of Jenkins. We heard that setting up Jenkins is hard, so we are giving you tools to make that simpler. There are instructions <https://cloud.google.com/tools/repo/push-to-deploy> explaining how to set up Jenkins and configure continuous deployment for your GCP apps, using provided plugins <https://cloud.google.com/tools/repo/push-to-deploy#jenkins_plugins>. With the availability of this solution, we are going to remove the Release Pipelines UI in the Developer Console by January 22. If you are currently using the build/test options, please remember to disable your pipeline so you are no longer charged for it. Note that repo sync with GitHub and Bitbucket is still supported and the Jenkins plugin to trigger a deployment from the push event is included above. If you used the 'source only' option in Release Pipelines, going forward you can use gcloud app update <https://cloud.google.com/sdk/gcloud-app> to deploy source to App Engine. If you have any questions, please email [removed]*. Google Cloud Release Pipelines team *I removed the email address in the event that it was reserved for current users. On Monday, December 22, 2014 2:57:20 PM UTC-6, Kristopher Giesing wrote: > > I'm confused as well, was there an official announcement that I missed? > > - Kris > > On Saturday, December 20, 2014 11:14:29 AM UTC-8, Chad Vincent wrote: >> >> Wait, what is this? >> >> I just spent 3 of the last 5 weeks trying to convert our Eclipse build to >> Maven so we could use push-to-deploy (and dependency management)... >> >> On Friday, December 19, 2014 9:22:57 PM UTC-6, Rae Wang wrote: >>> >>> Hi Lucas, >>> >>> I'm sorry this upsets you. I hear your need to have an easier source >>> deploy experience and will connect you offline with the eng team working on >>> the deployment. >>> >>> Thanks, >>> Rae >>> >>> On Friday, December 19, 2014 3:44:30 PM UTC-8, 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
