如何在 TFS 2012 RC 签入前强制进行代码审查? [英] How to force Code Review before Check-In in TFS 2012 RC?
问题描述
我刚刚安装了 TFS 2012 RC 和 Visual Studio 2012 RC.我看到了一些有趣的恐惧:代码审查、签入前建立成功.但它没有！所以我的问题是:
I've just installed TFS 2012 RC and Visual Studio 2012 RC. I see some interesting feartures: Code Review, Build Success before check-in. But it do not! So my question is:
- 如何在 TFS 2012 RC 中在签入前强制进行代码审查?
- 如何强制构建"签入政策(非门控签入)?
- Builds"签入政策和Gated Check-in"有什么区别?
推荐答案
1) 在团队资源管理器中，转到设置"部分.选择源代码管理".弹出窗口后，选择签入策略"选项卡.点击添加"并选择您需要的选项.
1) In team explorer, go to the "Settings" section. Choose "Source Control". When the window pops up, select the "Check-in Policy" tab. Click "add" and select the options you need.
2) 创建一个新版本.在触发器"选项卡上，更改为持续集成".这将在每次签入时强制构建.
2) Create a new build. On the "Trigger" tab, change to "Continuous Integration". This will force a build with every check in.
3) 门控签入需要成功的构建才能签入.持续集成 (CI) 在签入时构建(这两个选项都可以在构建设置的触发器选项卡上找到，您实际上可以在不同的构建中同时拥有这两个选项)门控签入基本上会将您的签入存储为变更集，在其上运行构建，并在构建失败时拒绝签入.CI 检查您的代码并运行构建，这可能会也可能不会失败.
3) Gated check in requires a successful build to check in. Continuous Integration (CI) builds on check in (both options are found on the trigger tab in the build settings, and you can actually have both on different builds) A gated check in will basically store your check in as a changeset, run a build on it, and deny the check in if the build fails. CI checks in your code and runs a build, which may or may not fail.
希望有帮助！
这篇关于如何在 TFS 2012 RC 签入前强制进行代码审查?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
