TFS 2010:在主分支上进行门禁登记；在 Dev 分支上滚动构建? [英] TFS 2010: Gated Check-In On Main Branch; Rolling Builds on Dev Branch?

问题描述

我最近从 VSS 迁移到 TFS 2010 并且我一直非常喜欢它，但我还没有能够按照我认为应该的方式工作.

I recently migrated from VSS to TFS 2010 and I've been absolutely loving it, but there's something I haven't yet been able to get working the way I think it should.

目标

我想快速知道何时对开发的更改破坏了构建.如果我们事后发现，这没什么大不了的.由于一整天都在发生大量签入，我们不想等待构建完成，所以它应该是异步的.

I'd like to quickly know when a change to Development breaks a build. If we find out after-the-fact, it's no big deal. Since a lot of check-ins happen throughout the day, we don't want to wait on the build to finish, so it should be asynchronous.

对于我们的主分支，我想确保任何时候合并发生时，我们都确保它不会破坏构建.我想立即得到反馈.等待时间很好，因为我们不会经常合并到 Main 中.

With our Main branch, I'd like to ensure that any time a merge happens into it, we make sure it's not going to break the build. I want immediate feedback on this. The wait time is fine, since we won't be merging into Main often.

当前设置

我的解决方案位于名为 Main 的文件夹下.我从名为 Development 的分支中创建了一个分支.我正在工作的工作区与顶层相关联，其中包括主分支和开发分支.我尝试将我的工作区调整为仅指向开发，以防出现问题.这似乎并没有解决我的问题，所以我把它设置回了我最初的方式——主要和开发.

My solution is under a folder called Main. I've made a branch off of that called Development. The workspace I'm working in is tied to the top-level, which includes both Main and Development branches. I tried adjusting my workspace to only point to Development, in case that was the problem. That didn't seem to fix my issue, so I set it back to the way I had it originally -- with both Main and Development.

在工作区的构建定义中，我定义了两个定义——一个用于主分支，另一个用于开发.

Within the workspace's Build definitions, I have two definitions defined -- one for the Main branch and another for Development.

第一个定义用于构建主分支.它有一个 Gated Check-In 触发器，Items to Build"指向 Main 中的解决方案文件.

The first definition is for building the Main branch. It has a Gated Check-In trigger and "Items to Build" points to the solution file within Main.

第二个定义用于在开发分支中构建解决方案.它有一个滚动构建触发器，构建项目"指向开发中的解决方案文件.

The second definition is for building the solution in the Development branch. It has a Rolling Builds trigger and "Items to Build" points to the solution file within Development.

结果

目前，当在开发中进行更改并执行签入时，会触发对 Main 的门控签入.这不仅会造成混乱，还会拖慢我们的整体流程.

Currently, when a change is made in Development and a check-in is performed, the gated check-in to Main is triggered. This not only causes confusion, but it also tends to slow down our overall process.

下一步

我查看了一些 TFS 分支指南、一般 TFS 用法等.不幸的是，我还没有找到解决我的问题的方法.如果您以前遇到过这个问题，我们非常感谢您提供任何建议.

I've looked at some of the TFS guides to branching, general TFS usage, etc. Unfortunately, I haven't yet found a solution to my issue. If you've run across this issue before, I'd appreciate any suggestions you can give.

推荐答案

我现在不是 100% 确定，但是构建应该由签入到构建定义工作区覆盖的源代码树.

I'm not 100% sure at the moment, but the build should be triggered by check-ins into the part of the source tree that is covered by the build definition workspace.

因此，请查看构建定义并查看每个构建定义获取源树的哪一部分.你的 CI 构建应该只得到 Dev 分支，门控构建应该只得到主分支.

So please have a look into the build definition and see what part of the source tree each build definition gets. Your CI build should only get the Dev branch, the gated build should only get the Main branch.

这篇关于TFS 2010:在主分支上进行门禁登记；在 Dev 分支上滚动构建?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！