问题描述
我们目前正在使用TeamCity，并计划由于组织需求/约束而移至BuildForge。我想对TeamCity和BuildForge进行功能比较。任何人都可以帮助我这个。我可以找到BuildForge与其他CI工具比较，如Hudson，CruiseControl。
We are currently using TeamCity and planning to move on to BuildForge because of organizational needs/constraints. I want to do a feature comparison on TeamCity and BuildForge. Could anyone please help me on this. As I could find comparison of BuildForge with other CI tools such as Hudson, CruiseControl only.
推荐答案
我会使用其他比较一个基线（尤其是相当接近的Hudson），基本上创建一个你关心的功能矩阵，看看哪些工具做什么。您可以要求IBM的分解。
I would use the other comparisons as a baseline (especially the Hudson one which will be quite close), and basically create a matrix of features you care about, and see which tools do what. You may ask IBM for their break-down.
一般来说，CI工具的大量功能列表（有关TC的数据）是CI比较矩阵：
和。
A great list of features for CI tools in general (with data on TC) is the CI comparison matrix: CI Feature Matrix and Comparison of Continuous Integration Software.
在Urbancode，我们的AnthillPro产品直接针对Build Forge，我们对特征矩阵的处理是在白皮书（需要注册）。
At Urbancode, our AnthillPro product competes pretty directly against Build Forge, our take on a feature matrix is in a white-paper "Continuous Integration and Build Management Server Evaluation Guide" (registration required).
基本上，我认为你会发现BF能够处理更大的环境（可扩展性，安全性，可扩展性类型优势），而TC更纯粹，团队级CI服务器（更广泛的集成和测试趋势类型活动）。
Basically, I think you'll find that BF is capable of handling a larger environment (scalability, security, scalability type strengths) while TC is more of pure, team level CI server (wider range of integrations, and test trending type activities).
这篇关于TeamCity与BuildForge的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！