它是可以接受的/好于SVN存储二进制文件？ [英] Is it acceptable/good to store binaries in SVN?
问题描述
我们想和大家分享的运行系统项目的二进制文件。所以，每一个团队成员可以采取当前的工作版本。
这是可以接受/好存储在SVN运行时二进制文件？
We would like to share runtime project binary files. So every team member could take current working version. It is acceptable/good to store runtime binaries in the SVN?
推荐答案
您可能要存储二进制文件的版本控制系统两种常见的原因是：
The two common reasons you may want to store binaries in a Version Control System are:
-
商店外部第三方库。结果
通常一个存储到Maven仓库，而是将其保存到SVN可以让你有 且只有一个参照的您的所有需求：让你的源代码，并获得库需要编译这些来源。所有这些都从一个资源库。
store external third-party libraries.
Usually one stores them into a Maven repository, but to store them into SVN allows you to have one and only one referential for all your need: get your sources, and get your libraries you need to compile those sources. All comes from one repository.
商店交付更快的部署。结果
通常交付（可执行构建部署到生产）是建立在需求的。结果
但是，如果你有很多pre-生产环境，如果你有很多的交付，建造他们组装，集成，亿安科技，pre-生产平台的成本会很高。结果
一个解决办法是建立一次它们，将它们存储在您的SVN的交付部分，直接在不同的环境中使用它们。结果
注：结果
这也适用于发展的要素：如果你有一个 JAXB 产生900 POJO文件（通过XML绑定）的过程，你需要下载开发在多种环境设置，可能需要1 COM pressed文件拷贝的交易，而不是900的。
store deliveries for quicker deployment.
Usually deliveries (the executable you build to deploy into production) are built on demand.
But if you have many pre-production environment, and if you have many deliveries, the cost of building them for assembly, integration, homologation, pre-production platforms can be high.
A solution is to build them once, store them in a deliveries section of your SVN, and use them directly in your different environment.
Note:
This apply also to development elements: if you have a Jaxb process which generates 900 POJO files (through XML binding), and you need to download that development set in multiple environments, you may want 1 compressed file copy transaction, rather than 900 ones.
所以，是的，它是接受/好于SVN存储运行的二进制文件......正确的原因。
So yes, it is "acceptable/good to store runtime binaries in the SVN"... for the right reasons.
话虽这么说：
- 维姆·科嫩理所当然中的提到的缺点（不好的做法，缓慢，资源和存储交付之间不匹配）
- 弗拉基米尔提倡使用交货参考的（Nexus设备或作为弗拉基米尔提到，的Apache常春藤）
- RogerV 说明的使用的优点说交付引用（的Nexus在他的案件）
- Wim Coenen rightfully mentions the disadvantages (bad practice, slow, mismatch between sources and stored delivery)
- Vladimir advocates for the use of a delivery referential (Nexus or, as Vladimir mentions, Apache ivy)
- RogerV illustrates the advantages of using said delivery referential (Nexus in his case)
这篇关于它是可以接受的/好于SVN存储二进制文件？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
