推送部署，管道，谷歌应用程序引擎 [英] Push to deploy, pipelines, google app engine

问题描述

GAE推送部署管道的地方在哪里？
我看到Jenkins和所有的新东西，但是旧的管道设置已经不存在了吗？花了10秒钟才设置好，最近效果很好。我仍然将它用于〜5个正在进行的生产环境。我需要将它用于下一个项目，但我找不到它。

如果所有其他项都失败了，我们是否必须使用Jenkins？它最终可能不是问题，但是我会质疑需要为自己的源代码部署 的行为付费。无论如何，这将是一个混乱的第一次设置。

解决方案

我收到此电子邮件，现在偶然发现它...我认为这说明了发生了什么。

您好，

快速，轻松和安全地部署您的代码是优质云开发者体验的重要组成部分。您已经使用
GCP上的发布管道功能推送部署，并给予
非常深刻的反馈。我们清楚地听到您希望获得更多
的灵活性和控制权。因此，我们决定将产品以
的方向移动。

我们不想提供少量选项的管道，而是提供
你完全灵活的詹金斯。我们听说设立Jenkins
很困难，所以我们正在给你提供工具来简化这个过程。有
指令解释了如何使用提供的插件为您的GCP应用程序设置Jenkins和配置连续的
部署。

解决方案，我们将在1月22日之前删除开发者控制台中的
发布管道UI。如果您
当前正在使用构建/测试选项，请记住禁用
您的管道，以便您注意，仍然支持与GitHub和Bitbucket的repo同步，并且
Jenkins插件通过push事件触发部署。
包括上面。

如果您在发布管道中使用仅源代码选项，则可以使用gcloud应用更新来部署源代码如果您有任何问题，请发送电子邮件至
[e-mail]。

Google云发布管道团队

粘贴电子邮件时，链接消失，因此文档的最后一个链接是： https://cloud.google.com/sdk/gcloud-app

我认为我应该能够继续部署源代码以实现Rexisting使用 gcloud app update 的项目...我还没有尝试过。

此主题为还涉及： https://groups.google.com/forum/#！ topic / google-appengine / XUIh7QlO37U
它明确指出现有项目应该能够继续像以前一样能够部署。新项目可能必须使用Jenkins ... hm。

没有像 gcloud app update 。相反，我们必须cd到app.yaml所在的项目文件夹中并运行：

gcloud preview app deploy。

但是FIRST（！）我们必须安装更多的东西（如果上面的命令失败了）：

gcloud组件更新应用程序

当然，这意味着没有推送，只有部署 。 Google与中央存储库没有任何关系。您必须为您自己托管回购...实质上，这与为我部署桌面GoogleAppEngineLauncher并没有多大区别。

Where did GAE push-to-deploy pipelines go? I see all the new stuff with Jenkins and all, but is the good old pipeline setup gone? It took like 10 seconds to setup and worked really well recently. I still use it for ~5 ongoing production environments. I am in need of using it for the next project, but I can't find it.

If all else fails, do we have to use Jenkins? It might not be a problem in the end, however I would question the need to be billed for act of deploying own source code. Anyway it would be a mess to setup at first.

解决方案

I did get this email, and now stumbled upon it... I think it states what's going on.

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 [e-mail].

Google Cloud Release Pipelines team

Links disappeared when pasting the email so the last link to the docs is: https://cloud.google.com/sdk/gcloud-app

I think I should be able to continue deploying source for rexisting projects using gcloud app update... I have yet to try though.

This thread is also related: https://groups.google.com/forum/#!topic/google-appengine/XUIh7QlO37U It specifically states that existing projects should continue to be able to deploy as we used to be able to. New projects would likely have to use Jenkins... hm.

There is no command like gcloud app update. Instead we have to cd into the project folder where the app.yaml is and run:

gcloud preview app deploy .

But FIRST(!) we have to install something more (if the above command fails):

gcloud components update app

Of course, this means that there is no "push", only a "deploy". There will be no relation to a central repository at Google. You have to host your own repo for that... in essence, this is not much different than deploying using the desktop GoogleAppEngineLauncher to me.

这篇关于推送部署，管道，谷歌应用程序引擎的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！