TFS变更集中的文件数是否有限制? [英] Is there a limit on the number of files in a changeset in TFS?

问题描述

我已经进行了一些搜索，但无法确定TFS中单个变更集中文件数是否有任何限制.

这是IntelliJ IDEA提出的，我们发现它正在拆分包含200个以上文件的变更集.我想争辩说，根本不应该有任何限制，或者如果有限制的话，至少该限制应该与TFS自己的限制相同.在 http://youtrack.jetbrains.net/issue/IDEA-上看到我针对此问题报告的缺陷. 54846 .

解决方案

更改集中的更改数量存储为CLR的int类型.因此，绝对有int.MaxValue或2,147,483,647的上限.我认为没有任何检查可以以任何其他方式限制更改的数量(尽管我可能会误会.)实际上，您很可能在达到该值之前很长时间就需要在服务器上处理磁盘空间争用.

Team Foundation Server的特定设计目标之一是处理大型变更集-特别是合并具有大量变更的大型功能分支-可以生成具有大量合并或合并/编辑变更的变更集.

简而言之，不.即使有，也有数百个几个数量级.应该没有理由将它们拆分为多个变更集-这样做只会给自己造成损害.这样做会损害可追溯性，并且基本上会退化为非原子系统(是的，CVS！)，并使存储库的状态不可靠.它会对持续集成，链接到工作项和构建以及整体可追溯性产生负面影响.想象一下，将合并中的一半签入分支……然后另一半签入.听起来像一场噩梦.

I've done some searching but have not been able to find out if there are any limits in TFS to the number of files in a single changeset.

This came up with IntelliJ IDEA where we found that it was splitting up changesets with >200 files. I want to argue that there shouldn't be any limit at all, or at least the limit should be the same as TFS' own limit, if there is one. See the defect I reported on this issue at http://youtrack.jetbrains.net/issue/IDEA-54846.

解决方案

The number of changes in a changeset is stored as the CLR's int type. So there's definitely an upper limit of int.MaxValue or 2,147,483,647. I don't think there are any checks to limit the number of changes in any other way (though I may be mistaken.) Realistically, you probably have disk space contention to deal with on the server long before you reach that value.

One of the specific design goals of Team Foundation Server was to deal with large changesets - particularly merging large feature branches with a lot of churn - which can produce a changeset with a large number of merge or merge/edit changes.

In short, no. And even if there was, hundreds is several orders of magnitude off. There should be no reason to split them into multiple changesets - you only do yourself a disservice by doing that. You're hurting traceability by doing this and basically devolving into a non-atomic system (yay, CVS!) and makes the state of your repository unreliable. It negatively impacts continuous integration, linking to work items and builds and overall traceability. Imagine checking in half your merges to a branch... then the other half. That sounds like a nightmare.

这篇关于TFS变更集中的文件数是否有限制?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！