选择有效的修订控制
我们是一家公司，致力于小型和大型项目。有时，一个项目有 5、10、20 等多个开发人员。
我们正在寻找一种有效的版本控制系统，具有最佳可选属性：
性能问题 - 单一文件大小、复杂的目录结构
可扩展性< /strong> – 支持 5、10、25 个开发人员，10、50、200 个项目
分支合并
代码更改的修订和标记
统计和报告针对开发者、领导者、供应商、领导者开发、客户等。
支持各种技术的开发——.NET、JAVA、PHP、Oracle、Delhpi、ABAP/SAP。
目前我们正在 SVN、VSS、Rationalrose、ClearCase 和 JIRA 之间做出选择。其中一些解决方案是否支持错误跟踪和知识库存储库？
也许有人在这个主题上有经验并可以提出建议。
提前致谢。
此致。
We are a company, working on small and some huge project. Sometimes on one project are more developers 5, 10, 20 etc.
We are searching for an effective revision control system with best optional properties:
Performance issues – one file size, complex directory structure
Scalability – support for 5, 10, 25 developers, 10, 50, 200 projects
Merging of branches
Revisioning and marking of code changes
Statistics and report for developers, leaders, vendors, leader development, customer etc.
Supporting the development of various technologies- .NET, JAVA, PHP, Oracle, Delhpi, ABAP / SAP.
At this moment we are deciding between SVN, VSS, Rational rose, ClearCase and JIRA. Does some of this solutions support bug tracing and knowledge base repository?
Maybe someone has experiences on this topic and could give proposals.
Thanks in advance.
Best regards.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
我曾在我工作过的多家公司从事过 SVN、VSS 和 Clearcase 的工作。我一直觉得SVN是其中最好的。然而，现在有一些更好的分布式版本控制工具（如 Mercurial、git、bazaar）可用，您可能也想考虑一下。
以下是我主要对 SVN/clearcase 的看法：
性能问题
SVN：我发现 subversion 可以处理最大 2GB 的单个文件。复杂的目录结构对于 subversion 来说并不重要
Clearcase：我在 Clearcase 处理大型文件/存储库时看到了性能/网络问题。就我而言，它是我的 Windows 系统中的 NFS 安装，它使执行构建时的速度变得非常慢。
可扩展性
SVN 和Clearase 具有良好的可扩展性选项。然而，svn 在互联网上有相当好的社区和支持，这是clearcase 所缺乏的。但是，如果使用 Clearcase，您将获得付费支持并快速解决任何可扩展性问题。
分支合并
在这种情况下，Clearcase 无疑是赢家。 Clearcase 一时拥有相当不错的合并功能。 SVN 在这方面仍在改进，但最近对 svn 合并功能做出了重大贡献。
代码更改的修订和标记
IMO，clearase 和 svn 之间几乎相同。但惯例略有不同。
统计和报告
Clearcase具有良好的报告功能，比svn更好。然而，我觉得在这种情况下，clearcase 是一个过度杀手。 SVN 有很多简单的报告工具（如 glassfish），能够提供简洁的报告。
支持各种技术的发展
我已经研究过上面的大部分技术，但我相信这两种工具都对所有可能的环境（如 Visual Studio、Eclipse 等）都有很好的支持。
顺便说一句，rationalrose 是一个 UML 工具，与版本控制无关。 JIRA 是一个错误跟踪工具，它与 SVN 集成良好。我建议您查看 trac 以与 svn 集成。
希望以上内容有帮助
I have worked on SVN, VSS and clearcase in various companies which I have worked with. I have always felt SVN is the best among these. However there are some better distributed version control tools(like mercurial, git, bazaar) available in the these days which you might want to consider too.
Here are my views primaryly on SVN/clearcase:
Performance issues
SVN: I have seen that subversion can handle things up to a single file size of 2GB. Complex directory structure does not matter for subversion as it is
Clearcase: I have seen performance/network problems in clearcase in handling huge files/repositories. In my case it was a NFS mount in my windows system and it had made things terribly slow while perfoming builds.
Scalability
Both SVN & clearase have good scalability options. However svn has pretty good community and support over the internet which lacks for clearcase. However in case of clearcase you will have a paid support and quick resolution for any scalability problems.
Merging of branches
Clearcase is a clear winner in this case. Clearcase for a while has a pretty good merge capablities. SVN is still improving on this front, but there has been a major contribution to the svn merge feature in the recent past.
Revisioning and marking of code changes
IMO, its pretty much the same between clearase and svn. But the conventions are a little different.
Statistics and report
clearcase has good reporting capabilities, better than svn. However I have felt clearcase is a over killer in this case. SVN has a lot of simple reporting tools(like glassfish) which are capable of providing neat reports.
Supporting the development of various technologies
I have worked on most of the technologies above but I believe both the tools have decent support for all possible environment( like Visual Studio, eclipse, etc)
BTW, rational rose is a UML tool, not related to versioning. JIRA is a bug tracking tool, it integrates well with SVN. I would recommend you look at trac for integrating with svn.
Hope the above helps
我们在 SVN 方面拥有非常好的经验。它对代码库有很好的控制，并且很容易看到文件发生了什么。
它还通过第 3 方插件具有良好的 Visual Studio 交互。我们使用VisualSVN，它不是免费的，但非常好。
VSS 不好。很容易把事情搞砸。
ClearCase 相当不错，但许可证非常昂贵。它通常对代码库有非常严格的控制，但是一旦出现问题就很难修复。
We have very good experience with SVN. It has good control on the codebase, and it is easy to see what has happened on the files.
It also has good Visual Studio interation via 3rd party plugins. We use VisualSVN, which is not free but is very good.
VSS is not good. It is very easy to mess up things.
ClearCase is quite good, but licenses are very expensive. It has generally very strict control on the code base, but should something go wrong it is very difficult to fix it.
不管怎样，不要使用 VSS。绝不。
据我所知， Jira 不是版本控制系统，而是一个错误/问题跟踪系统（而且是一个非常好的系统）。
正如其他答案中所说，SVN 是一个非常好的解决方案，被很多项目成功使用。较新的分布式解决方案包括 Git、Mercurial (Hg)、Bzr...但我不会在非分布式团队中使用分布式版本控制系统。了解 DVCS 确实需要初始成本。
我是否已经说过：在任何情况下都不要使用 VSS。
Whatever it takes, dont use VSS. Never.
As far as I know, Jira is is not a version control system, but a bug / issue tracking system (and a very good one).
As said in other answers, SVN is a very good solution, used by a lot of projects with success. Newer distributed solutions include Git, Mercurial (Hg), Bzr, ... but I would not use a distributed version control system in a non distributed team. There is a real initial cost to undertand DVCS.
And did I already said : dont use VSS, under no circonstance.
上面的列表主要包含老式的修订控制。我会不惜一切代价避免 VSS，因为它专门锁定文件 - 一次只有一个用户可以更改甚至检出文件。
如果您仍然想要单个本地化存储库，我会推荐 SVN。它易于使用，并且通过第 3 方工具具有良好的 Visual Studio 交互。
如果您需要 Microsoft 技术的完全集成解决方案（错误跟踪、源代码控制、持续集成等），我建议使用 TFS。
如果您计划进行大量分支/合并，请查看 Mercurial/GIT 以获得分布式源代码控制。
The list above contains mostly old-school revision control. I would avoid VSS at all costs as it locks files exlusivly - only one user can change or even check-out a file at a time.
If you still want single localized repository I would recommend SVN. it's easy to use and has good Visual Studio interation via 3rd party tools.
If you need a fully integrated solution for Microsoft technology (bug tracking, source control, continuous integration etc.) I recommend using TFS.
Check out mercurial/GIT for a distrubutes source control if you plan on a lot of branching/merging.