Push to deploy discontinued?

[Lucas Geiger]

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.)

[Rae Wang]

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

[Chad Vincent]

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)...

[Kristopher Giesing]

I'm confused as well, was there an official announcement that I missed?

- Kris

[Kyle Finley]

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 explaining how to set up Jenkins and configure continuous deployment for your GCP apps, using provided 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 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.

[Brad Abrams]

Thank you all for your feedback.  We are sorry to have to make this change.  As Kyle points out, we have connected with all the current users to let them know of the change of plans.  What we have heard from many users is that they wanted more flexibility to configure build and test options.  To address that we are recommending that they use Jenkins directly.  

With that said, I’d love to hear your feedback and thoughts.  Please drop me an email b...@google.com.  

thanks

..brad

--
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-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[Syrus Mesdaghi]

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.

[Monique]

Unsubscribe me

 Monique Y. Calloway  🌹

--

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-appengi...@googlegroups.com.
To post to this group, send email to google-a...@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.

[Brad Abrams]

Thanks for all your feedback on this change. We heard from many of you that, while the Jenkins-based solution we offer works 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 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

--

[bergstrom...@gmail.com]

Sorry I'm a bit confused as of how to exactly deploy a project.

For existing projects I always used "git push origin master" to push-and-deploy. How would existing projects do that now? Will they continue to work? It seems as from yesterday this stopped working (but then I heard that it started working again...) It would be nice to know the official stance on this, if it *should* work or not.

For new projects, we just have to use Jenkins, right? Or is there another way? That email, which we also received, stated that "gcloud app update" would work to deploy, but I don't think that's a working command at all. Please shed some light.

[Brad Abrams]

Thanks for following up -- I am sorry this is confusing.   

For Java developers, we recommend you use Jenkins as we describe here: 

https://cloud.google.com/tools/repo/push-to-deploy

does that help?

..brad

To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/49a123fe-1398-42a3-b7d5-b475783ed7fe%40googlegroups.com.

[Dustin Hoffmann]

Hey Brad, my use case is this: I have a new html/css/js based single page app that I am hosting on Google Cloud. The old pipeline ui is now gone, and I am not a fan of Jenkins. All I want to do is have a simple deploy on git push like it was previously. Is this possible for me?

[Brad Abrams]

We really want to enable that use case.  The infrastructure we used for that in the past has proven to not meet our reliability requirements, so we are actively building a replacement.  As soon as that replacement is ready, we will re-enable this functionality.

..brad

To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/83705dd9-df55-44f0-a3fe-7a86a42f32c2%40googlegroups.com.

[Dustin Hoffmann]

Thanks Brad, really looking forward to having that back in business!

[SS]

Dear Brad,
                  I just saw this. I have a PHP app deployed in GAE, can I use JENKINS?
Does Jenkins supports PHP app AUTO deployment for GAE?

Currently, I see only, JAVA, PY, GO support in the documentation.
Can you please clear this?

Thnks,
Ss

[Andrew Jessup]

Hi SS, we're testing PHP with Jenkins right now. I'll update this thread as soon as we've fixed up the documentation.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/c36c62cf-7f09-4216-9faf-a72e6dd2c459%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Andrew Jessup | Product Manager, Google Cloud Platform | jes...@google.com 

[SS]

Thnks Andrew fr ur instant reply.We are waiting eagerly for this news update.

Thnks,
Ss

[Andrew Jessup]

Hi SS, thanks for your patience. I've done some testing, you should be able to deploy PHP applications using Jenkins by following the instructions at:

https://cloud.google.com/tools/repo/push-to-deploy

These don't explicitly say how to deploy a PHP application, but fortunately it's exactly the same as for python apps (except for the "Build and Test" step, which will not work - but you can also safely ignore).

We'll get the documentation updated to describe how to deploy PHP applications shortly.

[SS]

Dear  Andrew,
            Thnks fr ur reply. We ll test it. We already have a GCE(Debian Linux) running w LAMP stack.

            So, should I install the below bitnami jenkins under GCE Debian platform to proceed further, since i cant use a second time 'Click to deploy JENKINS' under the same GCE instance
            https://bitnami.com/stack/jenkins/installer

            Also which plugins should I use for jenkins? Should I use the below one or use a specific PHP plugin fr Jenkins?   
            https://wiki.jenkins-ci.org/display/JENKINS/Google+Source+Plugin
            http://jenkins-php.org/

            As you mentioned, should I ignore these below steps fr BUILD & TEST under PHP deployements:

            Python
            If you have have implemented unit tests for your app, do the following:
                Select Execute Shell.
                    Enter the following in the Command text field:
                        nosetests --with-xunit --xunit-file=nosetests.xml

    Is so, how my PHP App will be auto built and tested(PHPUnit fr eg.) like xunit in Python?

    Thnks in advance fr ur help, very eager to setup this jenkin fr our dozens of PHP APP in GAE.Hope u ll help us.
    SS

[Andrew Jessup]

Hi SS,

We've only tested this with the documentation provided at 

https://cloud.google.com/tools/repo/push-to-deploy

which describes how to create a new Jenkins instance with the appropriate plugins and tools already installed. You may be able to re-use a different Jenkins instance to work with these instructions, or update one to use the same plugins and tools, but we don't have instructions for doing so at this time.

As for unit testing instructions for PHP, we will aim to to provide some shortly. We will likely need to update the image described in the documentation to do this however since we don't install PHPUnit by default.

[SS]

Dear Andrew,
             Thnks fr ur reply. Atleast, can you plz tell us which jenkins package/plugin we should use fr our existing GCE Debian?
             I gave some links in my previous reply, plz its very hard to select the package with the right PHP plugins.

             HoW will we know which package/plugins to install and which will support the google plugin or which one will support Google Auto deploy function? Totally we are blank. R u telling 
             that only people, who use 'Click to deploy' solution can use Google's above 'Push to Deploy' method? If so, its really hard for those who cannot use that option?
             That said, why Google doesn't support multiple 'Click to deploy' solutions under a same given GCE instance?

             Plz help Andrew.

             BR,
             Ss

[SS]

Hi Andrew,
                    Any updates for us fr our previous reply? We are struck and waiting for ur minimum guidance in Jenkins package selection.

Thnks in advance,
Ss

[Jeremie Laviolette]

Any updates on bringing back a simple deploy on git push like it was previously?