大型二进制文件和> 1TB存储库的版本控制？ [英] Version control for large binary files and >1TB repositories?

问题描述

很抱歉再次提出这个话题，因为有 soo 很多 其他已经相关的问题 - 但没有直接覆盖我的问题。

什么我搜索的是一个好的版本控制系统，它只能处理两个简单的需求：
$ b

1. 存储大型二进制文件（> 1GB） li>
   
2. 支持一个大于1TB的存储库（是的，这就是TB）

为什么？我们正在为我们的下一个大型操作系统部署重新包装几千个软件应用程序，我们希望这些包遵循版本控制。

到目前为止，我已经一些SVN和CVS的经验，但我对大型二进制文件的性能不满意（少数MSI或CAB文件大于1GB）。另外，我不确定它们是否能够很好地满足我们预计未来2-5年的数据量（就像我说的，估计大于1TB）

那么，你有什么建议吗？
我目前也在研究SVN Externals以及Git Submodules，尽管这意味着每个软件包都有几个单独的存储库，我不确定这是我们想要的。

解决方案

版本控制系统用于源代码，而不是二进制版本。只需使用标准网络文件服务器备份磁带进行二进制文件备份即可 - 尽管在您有源代码控制时基本上不必要，因为您可以随时重建任何版本的任何二进制文件。试图将二进制代码放在源代码控制中是一个错误。

你真正在谈论的是一个称为配置管理的过程。如果您有数千个独特的软件包，您的企业应该有一个配置管理员（一个人，而不是软件;-)）负责管理所有用于开发，测试，发布，每客户发布等配置（又称构建）。 。

Sorry to come up with this topic again, as there are soo many other questions already related - but none that covers my problem directly.

What I'm searching is a good version control system that can handle only two simple requirements:

1. store large binary files (>1GB)
2. support a repository that's >1TB (yes, that's TB)

Why? We're in the process of repackaging a few thousand software applications for our next big OS deployment and we want those packages to follow version control.

So far I've got some experience with SVN and CVS, however I'm not quite satisfied with the performance of both with large binary files (a few MSI or CAB files will be >1GB). Also, I'm not sure if they scale well with the amount of data we're expecting in the next 2-5 years (like I said, estimated >1TB)

So, do you have any recommendations? I'm currently also looking into SVN Externals as well as Git Submodules, though that would mean several individual repositories for each software package and I'm not sure that's what we want..

解决方案

Version control systems are for source code, not binary builds. You are better off just using standard network file server backup tapes for binary file backup - even though it's largely unnecessary when you have source code control since you can just rebuild any version of any binary at any time. Trying to put binaries in source code control is a mistake.

What you are really talking about is a process known as configuration management. If you have thousands of unique software packages, your business should have a configuration manager (a person, not software ;-) ) who manages all of the configurations (a.k.a. builds) for development, testing, release, release-per-customer, etc.

这篇关于大型二进制文件和> 1TB存储库的版本控制？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！