从 SVN Bridge 进行 TFS 代码审查？
是的，标题是正确的。有没有办法从通过 SVN Bridge 连接到 TFS 存储库的用户计算机对 TFS（Microsoft 的 Team Foundation Server）中存在的项目进行代码审查？
（相关：SVN Bridge 是一个允许使用 Subversion 工具连接到 TFS 存储库的工具）
为什么？因为我们有开发人员极力捍卫（至死）使用 SVN 而不是 TFS。这些高级开发人员将对第三方供应商的签入进行代码审查。
问题是该项目当前驻留在 TFS 中，并将保留在那里（根据 CTO 的指示）。我们可以使用 SVN Bridge，但我不清楚这些代码审查工具是否支持这种跨平台。
会怎样呢？嗯，我认为它会知道代码审查包中的文件。为什么它不能将这些文件与 SVN 目录而不是 TFS 进行比较？
促使我想到这个环境的是 Code Collaborator 的这个演示：
http://smartbear .com/docs/viewlets/CodeCollabDemo/CodeCollabDemo.html
屏幕截图：
请注意，在首先，它询问要审查哪个存储库？如果远程团队选择TFS，本地团队选择SVN怎么办？是的，我会就这个问题联系他们的技术支持。但我也想在这里向可能有类似设置的任何人发布这个问题。
提前致谢。
Yes, the title is correct. Is there a way to code review a project that exists in TFS (Microsoft's Team Foundation Server) from a user's computer that is connected to that TFS repository via an SVN Bridge?
(related: an SVN Bridge is a tool that allows the use of Subversion tools to connect to an TFS repository)
Why? Because we have developers that highly defend (to their death) the use of SVN over TFS. And these senior developers will be doing the code reviews of checkins from the the 3rd party vendor.
The problem is that the project currently resides in TFS, and will remain there (per CTO's instructions). We are allowed an SVN Bridge, but yet it is not clear to me if any of these code review tools support such a cross-platform.
How would it? Well, I would think that it would know the files in the code review package. Why can't it compare those files to an SVN directory instead of an TFS?
What prompted me to think of this environment is this demo of Code Collaborator:
http://smartbear.com/docs/viewlets/CodeCollabDemo/CodeCollabDemo.html
Screenshot:
Notice that at the begining, it asks for what repository to review? What if the remote team chooses TFS, and the local team chooses SVN? Yes, I'll ping their technical support for that question. But I also wanted to post the question here for anyone that may have a similar setup.
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您的 svn 桥接软件足够先进，Code Collaborator 只会将该存储库视为 svn 存储库，因此没有问题。 Code Collaborator 客户端（GUI 和命令行）都执行 subversion 命令行客户端（您可以指定其路径和名称）来获取其信息。如果你打开调试日志（通过命令行上的 --debug 或通过 GUI 中的帮助菜单），你甚至可以准确地看到正在执行的 svn 命令。只要那些输出与“真正的”颠覆兼容，你应该没问题，因为你的客户端只会将其视为 svn 存储库。
由于评论的作者通常是唯一将文件添加到评论的人，因此在同一评论中尝试将 TFS 中的文件与 Subversion-bridged-to-TFS 中的文件进行比较的问题不应出现 - 这很好，因为这实际上行不通，因为文件位于两个不同的 SCM 中。只要单个作者坚持使用一种 SCM 或另一种，就应该没问题。
（PS：我在 SmartBear 工作，从事 IT、开发和技术支持工作）
If your svn bridge software is sufficiently advanced, Code Collaborator will just see the repo as a svn repo, so there's no problem. The Code Collaborator Clients (GUI and commandline) all exec a subversion commandline client (that you can specify the path and name of) to get their information. If you turn on the debugging log (via --debug on the commandline or via the Help menu in the GUI) you can even see exactly what svn commands are being executed. As long as those have output compatible with 'real' subversion, you should be fine as your client will just see it as a svn repository.
Since the author of a review is usually the only person to add files to a review, the issue of trying to compare files in TFS to files in Subversion-bridged-to-TFS in the same review shouldn't come up - which is good, because that would actually not work since the files are in two different SCMs. As long as a single author sticks to one SCM or the other, you should be fine.
(PS: I work for SmartBear doing IT, development, and tech support)