Windows Azure 和持续集成

发布于 2024-12-04 01:54:33 字数 291 浏览 1 评论 0原文

我们希望建立持续集成(CI)环境来开发Azure Web应用程序。 那就太好了

  • 如果能够:我们可以使用任何流行的 CI 服务器(例如 Atlassian Bamboo),
  • 。每次构建时都会自动执行到测试环境的部署(与生产完全相同)。
  • 部署到生产环境是自动执行的,并通过选择一些稳定的构建手动触发。

实施此类场景的最佳实践是什么?

We would like to set up continuous integration (CI) environment for developing an Azure web application. It would be great if:

  • We could use any popular CI server (Atlassian Bamboo, for example).
  • Deployment to the test environment (exactly the same as production) is performed automatically on each build.
  • Deployment to the production environment is performed automatically and triggered manually by selecting some stable build.

What are the best practices for implementing such scenarios?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

扛刀软妹 2024-12-11 01:54:33

您可能想查看最近发布的对 Azure 持续集成和持续交付的内置支持。

对于本地构建服务器(带或不带 TFS),有以下指南:
http://www.windowsazure.com/en- us/develop/net/common-tasks/continuous-delivery/

对于 Team Foundation Service Preview(云中的弹性构建),有以下指南:
http://www.windowsazure.com/ en-us/develop/net/common-tasks/publishing-with-tfs/

对于 Git 和 Windows Azure 网站,这些链接旁边还有指导(我还不允许发布两个以上超链接..)。

you might want to check out the built in support for continuous integration and continuous delivery for Azure that came out recently.

For on premise build servers (with or without TFS) there is this guidance:
http://www.windowsazure.com/en-us/develop/net/common-tasks/continuous-delivery/

For Team Foundation Service Preview (elastic build in the cloud) there is this guidance:
http://www.windowsazure.com/en-us/develop/net/common-tasks/publishing-with-tfs/

For Git and Windows Azure Web Sites there is also guidance sitting next to these links (I'm not allowed yet to post more than two hyperlinks..).

嘿嘿嘿 2024-12-11 01:54:33

首先,您的部署过程需要在环境之间尽可能相似,以便要测试的部署能够与代码本身一起测试您的部署。良好的持续交付工具(我的公司提供一个)将对此有所帮助,并且在构建生命周期或构建管道中将这些阶段很好地结合在一起。

根据您的身份,在产品部署方面您需要考虑安全性和职责分离,同时为开发人员开放自助服务。

还要考虑是否要部署构建来成功测试该构建,但某些单元测试会失败。

Your deployment process, first and foremost, needs to be as similar as possible between environments so that a deployment to test, tests your deployment along with the code itself. Good continuous delivery tools (my company provides one) will help with that and tie those phases together nice in a build lifecycle or build pipeline.

Depending on who you are, you'll need to think through security and separation of duties when it comes to the prod deployment while leaving self-service open for developers.

Also think through whether you want to deploy builds to test that build successfully but fail some unit tests.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文