简体   繁体   English

使用TeamCity持续部署

[英]Continuous Deployment with TeamCity

I recently set up a CI server in TeamCity and now want to take it to the next step, continuous deployment. 我最近在TeamCity中设置了CI服务器,现在想要将其用于下一步,即持续部署。 Basically, we host a suite of restful services and about 3 web applications for each one of our customers. 基本上,我们为每个客户提供一套宁静的服务和大约3个Web应用程序。 All customers get 3 environments QA, UAT and Prod. 所有客户都获得3种环境QA,UAT和Prod。 We want to be able to automatically deploy our builds once our tests pass. 我们希望能够在测试通过后自动部署我们的构建。 I'm not looking for custom scripting options to do this. 我不是在寻找自定义脚本选项来做到这一点。 I've seen plenty of those of SO. 我见过很多SO。 What we're looking for is a solutions like UDeploy but at a lower price point. 我们正在寻找的是像UDeploy这样的解决方案,但价格较低。 Is anyone aware of alternatives to UDeploy? 有人知道UDeploy的替代品吗? Or other Continuous Deployment plugins that work with TeamCity? 或者与TeamCity一起使用的其他持续部署插件?

Thanks, 谢谢,

I agree with @Niklas Ringdahl -- I think you're thinking about it wrong. 我同意@Niklas Ringdahl - 我认为你错了。

You can deploy directly from TeamCity using MS WebDeploy . 您可以使用MS WebDeploy直接从TeamCity部署。

See Troy Hunt's excellent blog series about this: 请参阅Troy Hunt关于此的优秀博客系列:

Part 1: Config transforms 第1部分:配置转换

Part 2: MS Build and deployable packages 第2部分:MS Build和可部署的包

Part 3: Publishing with WebDeploy 第3部分:使用WebDeploy发布

Part 4: Continuous builds with TeamCity 第4部分:使用TeamCity进行持续构建

Part 5: WebDeploy with TeamCity 第5部分:使用TeamCity的WebDeploy

If this is .net you should look at Octopus, it now works nicely with TeamCity. 如果这是.net你应该看看Octopus,它现在可以很好地与TeamCity一起使用。

http://www.octopusdeploy.com/ http://www.octopusdeploy.com/

http://www.paulstovell.com/octopus/octopus-octopack-and-teamcity http://www.paulstovell.com/octopus/octopus-octopack-and-teamcity

I don't know if there's any part of this I don't understand, but I would use TeamCity for that also. 我不知道是否有任何我不理解的部分,但我也会使用TeamCity。

If you have a build configuration to manage your tests, you can easily create configurations for deploy, which are triggered by the success of the test configuration. 如果您有用于管理测试的构建配置,则可以轻松创建部署配置,这些配置由测试配置的成功触发。 We handle lots of our deploys that way. 我们以这种方式处理许多部署。

Again, sorry if I'm missing something here... 再次,抱歉,如果我在这里遗漏了一些东西......

EDIT : 编辑

A build configuration in TeamCity can be triggered when another configuration is successfully built: Build triggering in JetBrains documentation (Look at "Finish Build trigger") 成功构建另一个配置时,可以触发TeamCity中的构建配置: 在JetBrains文档中构建触发 (查看“完成构建触发器”)

Or you could use one build configuration with many "Build steps": Build steps in JetBrains documentation 或者您可以使用一个具有许多“构建步骤”的构建配置: 在JetBrains文档中构建步骤

Each step is run in order, and only if the previous step is successful. 每个步骤按顺序运行,并且仅在前一步骤成功时运行。

Another alternative: RedGate has recently updated pricing on their Deployment manager tool: http://www.red-gate.com/delivery/deployment-manager/ 另一种选择:RedGate最近更新了其部署管理器工具的价格: http//www.red-gate.com/delivery/deployment-manager/

If you have 5 projects or less, the tool appears to be free. 如果您有5个或更少的项目,该工具似乎是免费的。

我对Nolio ASAP很熟悉,但对其定价一无所知: http ://www.noliosoft.com/product/nolio-automation-center

As a developer for the product, I'll add BuildMaster to the list of options here. 作为该产品的开发人员,我将在此处将BuildMaster添加到选项列表中。 Basically, you can run a basic tutorial to get started deploying from TeamCity ( http://inedo.com/buildmaster/extensions/teamcity ), then customize your deployment plans to any further environments as needed. 基本上,您可以运行基本教程来开始从TeamCity( http://inedo.com/buildmaster/extensions/teamcity )进行部署,然后根据需要将部署计划自定义到任何其他环境。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM