Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Introduction
Enterprise Architect's version control integration provides numerous key facilities;
| • | Saving a history of changes to your model's packages |
| • | The ability to retrieve previous revisions of packages |
| • | Propagating model updates between team members |
| • | Coordinating sharing of packages between team members |
This section discusses some factors you should consider when setting up and using version control in your model development.
Topics
Topic |
Detail |
See also |
||||
|---|---|---|---|---|---|---|
Version Control Usage |
There are two main ways in which Enterprise Architect's projects can be deployed;
Version control is employed in the same way for both scenarios, however, when using Private Model deployment it serves the additional role of propagating model updates throughout the team. Version Control can also be used to share standard packages between different projects.
|
|||||
Version Control Basics |
Enterprise Architect must enforce serialized editing of version controlled packages, using the lock-modify-unlock mode of operation.
|
|||||
Applying Version Control to Models |
Using version control in Enterprise Architect consists of placing individual model packages under version control, rather than version controlling the project as a whole.
|
|||||
Version Control and Project Reference Data |
To ensure that changes in reference data are shared between users in a version-controlled project that is deployed as multiple private models, you should periodically export the reference data from the model where the changes were made, and import it into the other models maintained by the team.
|
|||||
Team Deployment |
You should consider the steps involved in setting up a version control environment and applying version control to an Enterprise Architect project to be accessed by a number of users.
|
|||||
Project Browser Indicators |
Packages under version control are identified in the Project Browser by icons that indicate the current status of the package.
|
|||||
Offline Version Control |
You can prevent Enterprise Architect from attempting to make any version control connections by choosing to Work Offline before loading a model. If Enterprise Architect is unable to connect a Version Control Configuration for any reason, it displays warning messages to notify you and provides 'offline' version control functionality for all packages associated with the failed connection.
|
|
||||
System Requirements and Configuration |
To use version control in Enterprise Architect, a third-party source-code control application is required that controls access to and stores revisions of the controlled packages. Typically there are:
Enterprise Architect uses the client component to communicate with the server. A version control client must be installed on every machine where you run Enterprise Architect and want to access your version control system.
|
