TFS 2010自动化部署流程
我试图了解 TFS 2010 中的自动化部署过程。
我有 DEV、QA、Stage 和 Live 环境。使用基本（或标准分支策略），在配置自动构建/部署时，部署到 DEV 时会从 MAIN 分支获取代码到 DEV 服务器。那么，如果我想让代码进入 QA，DEV 服务器上的位是否会进入 QA 服务器？然后从 QA 服务器获取数据到 Stage？最后从舞台到现场？因此，一旦代码从 TFS 转移到 DEV，只需将源代码从每个服务器移动到下一个服务器即可？
或者通常是从 DEV 分支（而不是 MAIN 分支）获取代码以转到 DEV 服务器，然后如上所述将代码移动到每个服务器？
只是想了解自动化部署过程以及什么是标准配置。
感谢您提供的任何信息...
I am trying to understand the automated deployment process in TFS 2010.
I have a DEV, QA, Stage, and Live environments. Using a basic (or standard branching strategy), when configuring automatic builds/deployments does deploying to DEV get code from the MAIN branch to the DEV Server. Then if I want code to go to QA, do the bits on the DEV Server go to QA Server? Then get bits from QA Server to Stage? And finally from Stage to Live? So once code goes from TFS to DEV it's just a matter of moving source code from each Server to the next?
Or is it typical to grab code from DEV branch (instead of MAIN branch) to go to DEV Server and then move code to each Server as described above?
Just trying to understand the automated deployment process and what is a standard configuration.
Thanks for any info given...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
TFS 没有单一的内置自动化部署过程。您需要根据项目类型指定代码的部署方式和位置。
部署是指部署成功构建的结果。部署仅在您构建分支时才涉及分支。
TFS does not have a single built-in automated deployment process. You need to specify how and where your code will be deployed, depending on the type of project.
Deployment is about deploying the results of a successful build. Deployment is about branches only to the extent that you have built a branch.
部署的目标是将分支的代码发送到环境。
因此，如果您在 MAIN 分支中工作并选择部署到 DEV，则来自该 MAIN 分支的代码将被部署（复制、安装等）到配置为 DEV 环境的任何内容。
大多数人的每个环境都没有一个分支。您可能会有一个与 MAIN 分支分开的 DEV 分支，但这是与自动化部署分开的源代码控制管理问题。您可能想按照这些思路重新标记这个问题。
The goal of deployment is to send a branch's code to an environment.
So, if you are working in the MAIN branch and choose to deploy to DEV, the code from that MAIN branch would get deployed (copied, installed, et al) to whatever is configured as the DEV environment.
Most people do not have one branch per environment. You probably would have a DEV branch separate from the MAIN branch, but that's a source control management concern separate from automated deployment. You might want to retag this question along those lines.