TFS与JIRA/Bamboo/SVN [英] TFS vs. JIRA/Bamboo/SVN

查看:168
本文介绍了TFS与JIRA/Bamboo/SVN的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

本周,我参加了2008 TFS的演讲.目前,我们正在使用Jira和Svn(也许还有Bamboo).您喜欢哪种解决方案?

this week I participated a presentation of the 2008 TFS. Currently we are using Jira and Svn (and maybe Bamboo). What solution to you prefer?

推荐答案

如果您仅使用TFS进行源代码控制,则别无其他(顺便说一句,这与租用喷气式飞机快上飞机一样,是过大的杀伤力)食物),那么最好使用只做源代码控制(SVN等)的较小解决方案. TFS是一种应用程序生命周期管理"(ALM)工具,并包含了大量的附加功能:

If you're just using TFS for source control and nothing else (which, btw, is overkill in the same way as chartering a jet to go pick up fast food), then you're better off with smaller solutions that just does source control (SVN, etc). TFS is an "Application Lifecycle Management" (ALM) tool, and incorporates a ton of additional functionality:

  • 错误跟踪
  • 开发者任务
  • 外部问题提交
  • 自动构建
  • 代码报告
  • 项目状态更新/时间预测
  • 还有很多

将其与仅执行源代码控制的工具进行比较并不十分公平-如果您这样做,TFS将显得既麻烦又昂贵.有可用的工具来完成所有这些事情,并且在大多数情况下它们甚至可以很好地集成在一起,但是特别是如果您的开发人员都在使用Visual Studio(并且总是

It's not really fair to compare it against tools that just do source control - TFS will appear cumbersome and expensive if you do. There are tools out there that can be used to do all these things, and they even integrate well together in most cases, but especially if your devs are all using Visual Studio (and there's always http://www.teamprise.com/ if some aren't) and you have some Sharepoint knowledge in-house, and ESPECIALLY if your devs have MSDN licenses (MSDN includes a CAL for TFS, so you only need to buy the server license), TFS can't be beat.

这篇关于TFS与JIRA/Bamboo/SVN的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆