从 Team Build Server 将网站部署到生产环境
我有一个带有构建服务器的团队基础服务器，当我运行构建时，它会部署到该盒子上的网站。不过，我也想在生产中执行相同的操作，生产是外部网络上的服务器，而不是同一域的一部分。
我考虑过查看 TFS Deployer，但这似乎只在网络中工作，一旦有机会我就会对其进行测试，但我认为最好的想法是在处理如此重要的事情时在这里询问。
拥有一种轻松部署到生产环境的方法真的是一个坏主意吗？
这里有人使用任何方法部署到生产中吗？你怎么做？
本质上，被接受的答案将交给那些能够告诉我实现部署的最佳方法的人，但只要它不是太明显，为我指明正确的方向就肯定会得到赞成票。
I have a team foundation server with build server, when I run a build it deploys to a website on that box. However I also want to do the same on Production which is a server on an external network and not part of the same domain.
I thought about looking at TFS Deployer but that just seemed to work within a network, I'm going to test it out as soon as I get a chance but I thought the best idea was to ask here when working with something so critical.
Is it a really bad idea to have a way of easily deploying to production?
Does anyone here deploy to production using whatever method? How do you do it?
Essentially the accepted answer will go to the person who can tell me the best method for achieving a deployment but pointing me in the right direction is sure to get an up vote as long as it's not too obvious.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
根据您可用的基础设施，您可以使用 wix 创建 msi，并使用 SMS 配置管理器将它们部署到目标集合。这是我们正在迈向但尚未达到的方向。我们还将 wix 集成到我们的构建过程中以创建 MSI 工件。我们想要走这条路的原因是因为我们使用 CruiseControl.net 作为我们的持续集成服务器，并且我们有一个 nant 脚本用于执行构建过程和部署过程。它们在 nant 文件中都是单独的目标，但我们想要的是对包括生产在内的所有环境的部署的一致模型。
目前我们正在做的是手动将 zips（这是我们当前构建过程的工件）移至生产环境。当 zip 在生产环境中解包时，我们必须从 zip 中删除所有 web.config、app.config 等，如果我们在配置中有新条目，则它们是手动创建的。
Depending on the infrastructure you have available to you you can use wix to create msi's and use SMS configuration manager to deploy them to a target collection. This is the direction that we are moving to but have not reached yet. We also integrated wix into our build process to create the MSI artifacts. The reason we wanted to go down this path was because we are using CruiseControl.net as our continuous integration server and we have a nant script that we use to perform both the build process and the deployment process. They are both separate targets in the nant file, but what we wanted was a consistent model of deployment to all environments including production.
What are are doing currently is we are manually moving zips (which are artifacts of our current build process) to production. When the zips are unpackaged in the production environment we have to remove all the web.config, app.config etc from the zips and if we have new entries in the configs they are made manually.
找到 msdeploy http://blogs.iis.net/msdeploy/archive/2008/01/22/welcome-to-the-web-deployment-team-blog.aspx
Found msdeploy http://blogs.iis.net/msdeploy/archive/2008/01/22/welcome-to-the-web-deployment-team-blog.aspx