We currently use BugZilla for bug/issue tracking, but are looking for other solutions which hopefully fits us better.
我们目前使用BugZilla进行错误/问题跟踪,但正在寻找其他希望更适合我们的解决方案。
One of the features we really would like is integration with both SVN and TFS, as we use both internally (java folks use SVN, .NET folks use TFS), but I have yet to find any who does both. Many do integrate with SVN, but I haven't found any but TFS itself that integrates with TFS SCM. Are there any other at all?
我们真正想要的一个功能是与SVN和TFS集成,因为我们在内部使用(java人使用SVN,.NET人员使用TFS),但我还没有找到任何两者兼顾的人。很多都与SVN集成,但我没有找到任何与TFS SCM集成的TFS本身。还有其他吗?
EDIT: Thanks to both Martin and gregmac for your responses. I'll take this information with me in our further investigation in what to do.
编辑:感谢Martin和gregmac的回复。在我们进一步调查该怎么做时,我会把这些信息带给我。
(If I could, I would set both your answers as THE answer to my question, but gave that one to gregmac for having a little less rep than Martin and that SvnBridge might let us keep TFS source control ;)
(如果可以的话,我会将你的答案设置为我的问题的答案,但是给了gregmac,因为他的代表比Martin少,而且SvnBridge可能让我们保持TFS源代码控制;)
2 个解决方案
#1
You could try SvnBridge,which makes your TFS server look like an SVN server. This would allow you to have Bugzilla or whatever point to multiple SVN servers - or if it doesn't support that, you could set the TFS svn repository up as an svn:external.
您可以尝试SvnBridge,它使您的TFS服务器看起来像SVN服务器。这将允许您拥有Bugzilla或任何指向多个SVN服务器 - 或者如果它不支持,您可以将TFS svn存储库设置为svn:external。
The otherside, I'd agree with Martin and say if you're looking to integrate everything together, then you should probably just integrate your repository as well, and get the .NET to use svn (since SVN is more portable than TFS). I'd highly recommend VisualSVN for this - it integrates very well with VisualStudio.
在其他方面,我同意Martin并说如果你想要将所有东西集成在一起,那么你应该只是整合你的存储库,并让.NET使用svn(因为SVN比TFS更便携)。我强烈推荐VisualSVN - 它与VisualStudio很好地集成。
There is of course going to be a learning curve, because SVN / VisualSVN will be different from TFS.. but if you can overcome that, and having shared bug tracking across the company is a big enough win, you should come out ahead.
当然会有一个学习曲线,因为SVN / VisualSVN将与TFS不同。但是如果你能够克服这一点,并且在整个公司内共享错误跟踪是一个足够大的胜利,那么你应该走在前面。
#2
This is going to look like shameless self promotion, but you might want to look at Teamprise for hooking your Java guys into the TFS repository. We have lots of happy customers who are doing just that.
这看起来像无耻的自我推销,但你可能想看看Teamprise将你的Java人员挂钩到TFS存储库。我们有很多满意的客户。
Alternatively you could try using the TFS Migration and Sync toolkit to link your SVN and Bugzilla repositories together with TFS, however it is non-trivial and I have yet to meet someone who has managed to do that satisfactorily.
或者,您可以尝试使用TFS迁移和同步工具包将您的SVN和Bugzilla存储库与TFS链接在一起,但这是非常重要的,我还没有遇到能够令人满意地完成这项工作的人。
In the interested of fairness I should also point out that you could also probably get the .NET folks to use the open source stack that the Java teams are using - however getting the integration working between the work item tracking, version control and build subsystems in that stack would be non-trivial and not likely to give them the experience they are used to.
为了公平起见,我还应该指出,你也可能让.NET人员使用Java团队正在使用的开源堆栈 - 但是在工作项跟踪,版本控制和构建子系统之间进行集成。这个堆栈将是非平凡的,不太可能给他们他们习惯的经验。
#1
You could try SvnBridge,which makes your TFS server look like an SVN server. This would allow you to have Bugzilla or whatever point to multiple SVN servers - or if it doesn't support that, you could set the TFS svn repository up as an svn:external.
您可以尝试SvnBridge,它使您的TFS服务器看起来像SVN服务器。这将允许您拥有Bugzilla或任何指向多个SVN服务器 - 或者如果它不支持,您可以将TFS svn存储库设置为svn:external。
The otherside, I'd agree with Martin and say if you're looking to integrate everything together, then you should probably just integrate your repository as well, and get the .NET to use svn (since SVN is more portable than TFS). I'd highly recommend VisualSVN for this - it integrates very well with VisualStudio.
在其他方面,我同意Martin并说如果你想要将所有东西集成在一起,那么你应该只是整合你的存储库,并让.NET使用svn(因为SVN比TFS更便携)。我强烈推荐VisualSVN - 它与VisualStudio很好地集成。
There is of course going to be a learning curve, because SVN / VisualSVN will be different from TFS.. but if you can overcome that, and having shared bug tracking across the company is a big enough win, you should come out ahead.
当然会有一个学习曲线,因为SVN / VisualSVN将与TFS不同。但是如果你能够克服这一点,并且在整个公司内共享错误跟踪是一个足够大的胜利,那么你应该走在前面。
#2
This is going to look like shameless self promotion, but you might want to look at Teamprise for hooking your Java guys into the TFS repository. We have lots of happy customers who are doing just that.
这看起来像无耻的自我推销,但你可能想看看Teamprise将你的Java人员挂钩到TFS存储库。我们有很多满意的客户。
Alternatively you could try using the TFS Migration and Sync toolkit to link your SVN and Bugzilla repositories together with TFS, however it is non-trivial and I have yet to meet someone who has managed to do that satisfactorily.
或者,您可以尝试使用TFS迁移和同步工具包将您的SVN和Bugzilla存储库与TFS链接在一起,但这是非常重要的,我还没有遇到能够令人满意地完成这项工作的人。
In the interested of fairness I should also point out that you could also probably get the .NET folks to use the open source stack that the Java teams are using - however getting the integration working between the work item tracking, version control and build subsystems in that stack would be non-trivial and not likely to give them the experience they are used to.
为了公平起见,我还应该指出,你也可能让.NET人员使用Java团队正在使用的开源堆栈 - 但是在工作项跟踪,版本控制和构建子系统之间进行集成。这个堆栈将是非平凡的,不太可能给他们他们习惯的经验。