DBMS或SVN中的集中存储库 [英] Centralized repository in DBMS or SVN
问题描述
我正在建立一个集中式存储库来存储企业架构师（来自sparx系统）生成的工件，以供6-8人的团队使用。最初考虑托管一个PostgreSQL数据库来集中存储工件，然后出现的另一个选择是使用SVN。在查看EA文档时，对于所考虑的选项的优缺点尚不清楚。与使用SVN相比，我在使用DBMS时有以下开销。
I am working on setting up a centralized repository to store enterprise architect (from sparx systems) generated artifacts for the team of 6-8 people to use. Initially thought of hosting a PostgreSQL database to store the artifacts centrally and the other option that came up was to use SVN. Looking at the EA documentation, not getting a clear idea on what are the pros and cons for the options in consideration. As compared to using SVN I have the following overheads while using a DBMS.
- 托管和管理DBMS
- DBMS的用户配置和管理
- 需要分别进行工件版本控制
- DBMS的备份等
- Hosting and managing DBMS
- User provisioning and management for DBMS
- Artifact Versioning need to done separately
- Backup etc for the DBMS
对于SVN，从EA文档中提到，该部署模型仅适用于最大大小为10的团队，并且可能会损坏文件。除此之外，使用SVN托管存储库是否存在任何瓶颈？听到在多用户环境中与Enterprise Architect合作过的人们的建议，真是太好了。
For SVN, from EA documents it is mentioned that the deployment model is suited for a team of maximum size 10 only and there is a possibility of files getting corrupted. Other than these are any bottlenecks in using SVN to host the repository ? It would be great to hear suggestions from folks who has worked with Enterprise architect in multi-user environment.
推荐答案
最多10个人员警告是指您的团队共享一个.EAP文件的情况。如果所有用户都有他们自己的.EAP文件，或者您没有设置DBMS存储库，则此方法将不适用。
The "maximum 10 people" warning refers to a situation where you have a team sharing a single .EAP file. It does not apply if all users have their own .EAP file, nor if you set up a DBMS repository.
在DBMS设置中，建议使用EA的基线作为版本管理，而不是外部版本控制存储库。这个概念是相似的：单个软件包是基准，但是它们不是将版本外部存储在SVN / CVS / etc中，而是内部存储在数据库中。
In a DBMS setup, I recommend using EA's baselines for version management, not an external version control repository. The concept is similar: individual packages are baselined, but instead of storing the versions externally in SVN/CVS/etc, they are stored internally in the database.
需要管理的存储库要少一些，但还应注意，将DBMS与外部版本控制结合使用时，EA会出现问题，这可能会令人烦恼，甚至（最坏的情况）会导致信息丢失。外部版本控制旨在与.EAP文件一起使用。
This gives you one less repository to manage, but it should also be noted that EA has issues when combining DBMS with external version control which can be annoying or even (worst case) cause information loss. External version control is intended for use with .EAP files.
基线比外部版本控制有一个很大的优势：您可以在EA中直观地比较不同的版本，并查看添加了什么，删除，更改和移动到各个图中。最大的缺点是：基线版本的程序包在项目浏览器中没有像版本控制程序包那样用特殊的图标表示。
Baselines have one big advantage over external version control: you can compare different versions visually inside EA and see what's been added, deleted, changed and moved in individual diagrams. The big disadvantage: baselined packages aren't indicated with special icons in the project browser the way version-controlled packages are.
带有单独的.EAP文件和外部的部署模型版本控制使人们可以选择将不同的程序包以及这些程序包的不同版本导入其EA项目。使用DBMS模型时，只有一个EA项目，因此每个人总是看到相同软件包的相同版本。
The deployment model with individual .EAP files and external version control gives people the option of importing different packages, and different versions of those packages, into their EA projects. With the DBMS model there is only one EA project, so everyone always sees the same versions of the same packages.
是的，对于DBMS，您需要设置用户并实施备份计划。但是您也需要备份SVN存储库以及团队成员的单个.EAP文件。
Yes, with a DBMS you need to set up users and implement a backup plan. But you need backups for SVN repositories too, and for the team members' individual .EAP files.
DBMS EA中的用户管理是一个两步过程。每个用户都需要对数据库具有读/写访问权限，每个人在EA项目中还需要一个单独的帐户。通过从Windows域导入，可以很容易地创建这些文件。
User management in EA on DBMS is a two-step process. Each user needs read/write access to the database, and each person also needs a separate account in the EA project. These can be easily created by importing from the Windows domain.
这是假设您在项目中打开了用户安全性，您绝对希望这样做是为了防止并发编辑问题。
This is assuming you switch on user security in the project, which you most definitely want to do in order to prevent concurrent-editing problems.
我对团队设置的建议始终是DBMS +用户安全+基线。它为您提供了一个EA工件的单一位置，每个人总是看到相同的东西。
My recommendation for a team setup is always DBMS + user security + baselines. It gives you a single location for the EA artifacts, and everyone is always seeing the same thing.
这篇关于DBMS或SVN中的集中存储库的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
