用于生成4GB ISO的构建系统的版本控制解决方案 [英] Version control solution for a build system that produces a 4GB ISO
问题描述
我有一个软件项目，在其构建的最后阶段，在创建所有的jar文件和相关的脚本/配置文件后，我需要植入一个CentOS ISO具有kickstart配置文件，运行一些安装后脚本并安装一些自定义的RPM。
I have a software project that at the last stage of its build, after creating all the jar files and related scripts/configuration files, I need to plant it in a CentOS ISO that has a kickstart config file that runs some postinstall scripts and installs some customized RPMs.
项目位于SVN存储库上，并从那里构建。我无法将iso的文件插入存储库，因为SVN不处理4GB存储库。
另一方面，问题是ISO中的一些RPM可能会从版本更改为版本，当我想构建一个旧版本的项目，我在一个坏的地方，因为RPMs是不是在SVN存储库。
The project is on an SVN repository and being built from there. I can't insert the files of the iso into the repository because SVN doesn't handle a 4GB repository. On the other hand, the problem is that some of the RPMs in the ISO might change from version to version, and when I want to build an older version of the project I'm in a bad place because the RPMs are not in the SVN repository.
有没有一个好的版本控制解决方案，我可以只使用4GB的ISO可以处理这个数量的数据？
有没有一个非版本控制的解决方案，我想做什么？
Is there a good version control solution that I can use just for the 4GB of ISO that can handle this amount of data? Is there a non-version-control solution to what I'm trying to do?
我宁愿生产尽可能少的变化，现有的SVN存储库的结构，因为有许多脚本和依赖它的东西。
I would prefer to produce as less changes as possible to the existing SVN repository's structure, as there are many scripts and stuff that depend on it.
将欣赏各种答案和建议。
Will appreciate all kinds of answers and suggestions.
谢谢！
推荐答案
如果你真的需要存储大的工件（ISO，RPM，...）for其中：
If you really need to store large artifacts (ISO, RPM, ...) for which:
- 您不需要比较不同版本之间的差异
- 不需要并行演化（只读工件）
那么你实际上不需要VCS（版本控制系统）。
then you don't actually need a VCS (Version Control System).
您需要一个工件存储库，例如 Nexus 。
请参阅在VCS中存储.jar文件的最佳做法（SVN，Git，...）
You need an artifact repository, like for instance Nexus.
See "Best practice to store .jar files in VCS (SVN, Git, …)"
您将在SVN repo
You will version in your SVN repo a text file with the necessary references to the artifact repository and its SHA1/MD5 key used when said artifacts have been stored.
这两个存储库的组合将允许完整的重现性， （根据存储库大小），因为工件存储库（与VCS相反）仅受磁盘空间限制。
The combinations of those two repositories will allow complete reproducibility, while scaling nicely (in term of repository size), since an artifact repository (contrary to a VCS) is only limited by disk space.
这篇关于用于生成4GB ISO的构建系统的版本控制解决方案的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
