问题描述
我们正在使用TFS2017 U1和更新的构建系统和TFVC。当我们准备在发布过程中将更改发布到下一个阶段时，我们会将所有变更集合并到下一个分支。我们有一个脚本可以同时自动关联所有相关的
工作项。有时，这会导致变更集与60-80个工作项相关联。
We're using TFS2017 U1 with the newer build system and TFVC. When we are ready to release a our changes to the next stage in our release process, we merge all changesets up to the next branch. We have a script that automatically associates all the relevant work items at the same time. Sometimes, this results in the changeset being associated with 60-80 work items.
我们可以看到每个工作项都与合并变更集相关联，但构建本身只列出了50个工作项。因此，然后更新工作项的构建脚本只能看到50个工作项，我们最终必须查找错过的
并手动更新它们。它还抛弃了TFS版本报告，因为它只列出了构建链接到它的工作项。我找不到任何其他对此限制的引用，所以想知道它是否对我们来说是独一无二的。它相当令人恼火。
We can see that each work item is associated with the merge changeset, but the build itself only lists 50 work items. As such, the build script that then updates the work items can only see the 50 work items and we end up having to look for the ones that were missed and update them manually. It also throws off the TFS release reports as that only lists the work items that the build has linked to it. I can't find any other references to this limit so wonder if it's unique to us. Its rather irritating.
谢谢你b $ b
推荐答案
感谢您在此发帖。
我检查并转载了这个问题。它确实只在构建摘要中显示了50个相关的工作项。暂时找不到任何官方文件。
I checked and reproduced this issue. It indeed only displayed 50 associated work items in build summary. Can not find any official documents to the limits for now.
我们已提交反馈
here ，请关注它以获取更多信息。
We have submitted a feedback here, please have focus on it for any further information.
谢谢和最诚挚的问候。
这篇关于构建的关联工作项目限制为50个工作项的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！