TFS：数百个独立的应用程序/项目 - 最好的方法是什么？
假设该公司拥有大量独立的中小型应用程序，这些应用程序可以在逻辑上分为少量组。
例如，我可以有宝马，马自达，本田，福特......，川崎，哈雷......总共几十个甚至数百个应用程序。
我认为 TFS 中有 2 个选项：
为每个应用程序创建一个单独的项目。 我最终会处理很多小项目，并且可能会受到限制，但好处是我可以将所有工作项、错误、报告等单独分配给每个项目，并为每个项目提供一个门户。
创建项目“汽车”和项目“摩托车”，并为每个项目下的每个应用程序创建一个带有分支的源代码控制树。 这将提供更好的结构和更少的开销，但我不能再分别为“Honda”和“BMW”分别拥有门户和工作项、错误、报告等列表。
我错过了什么吗？ 有没有一种方法可以同时拥有这两者 - 每个小项目的单独工作项列表和错误，而无需创建大量项目的开销以及达到项目数量限制的 TFS 风险？
Let's say that the company has a large number of separate small to medium applications which can be logically divided into a small number of groups.
For example, I can have BMW, Mazda, Honda, Ford .... , Kawasaki, Harley, .... altogether a few dozens or even hundreds of applications.
I think I have 2 options in TFS:
Create a separate project for each application. I end up with lots of small projects and can be hit by the limit, but the benefit is that I can have all workitems, bugs, reports etc. assigned separately to each project and have a portal for each project.
Create a project 'Cars' and a project 'Motorcycles', and create a source control tree with a branch for each application under each project. That will provide a better structure and less overhead, but I cannot have a portal and a list of workitems, bugs, reports etc. separately for 'Honda' and separately for 'BMW' anymore.
Am I missing something? Is there a way to have both - a separate list of workitems, bugs for each small project without the overhead of creating heaps of projects with the risk of hitting the TFS limit on the number of projects?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我会同意第 2 点。您可以使用 TFS 的“区域”部分将工作项分配给特定的子项目。
为所有这些小型应用程序创建完整的团队项目的开销太大。 每个应用程序是否都需要完全独立的生命周期、协作工具（WSS 站点）和一组报告？ 通常不会。
最坏的情况是，如果项目太大而无法管理，您可以为其中任何一个创建一个新的团队项目，因为当您创建项目并进入源代码控制屏幕时，有一个选项“从现有项目分支”，因此您可以用它来保存您的源历史记录并创建一个专用项目。
敏捷开始，根据需要扩展。
I would go with point 2. You can use the 'Areas' section of TFS to assign work items to a particular sub-project.
There is way too much overhead in creating full Team Projects for all those small apps. Does each of those apps need a completely independent life cycle, collaboration tool (WSS site) and set of reports? Usually not.
Worst case you can then create a new team project for any of them if it gets too big to manage, because when you create projects and get to the source control screen, there is an option to 'branch from existing project' so you could just use that to keep your source history and create a dedicated project.
Start agile, scale as needed.