Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Enterprise Architect's Version Control integration provides several key facilities, including:
- Saving a history of changes made to your model's Packages
- Retrieving previous revisions of Packages
- Propagating model updates between team members
- Coordinating the sharing of Packages between team members
The steps involved in setting up a Version Control environment and applying Version Control to an Enterprise Architect project that is to be accessed by a number of users, are summarized in the Help topic Applying Version Control in a Team Environment.
There are a number of factors to consider when setting up and using Version Control in your model development.
Factors to consider
System Requirements and Configuration
You apply Version Control through a third-party source-code control application that manages access to and stores revisions of the controlled Packages.
Typically the configuration consists of:
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.
Version Control Usage
There are two main ways in which projects can be deployed:
Version control is employed in the same way for both scenarios; however, when using Private Model deployment you have the additional facility of propagating model updates throughout the team.
Version Control can also be used to share standard Packages between different projects.
|Version Control Usage
Consider the process of setting up a Version Control environment and applying Version Control to a project to be accessed by a number of users.
|Applying Version Control in a Team Environment
Version Control Basics
Enterprise Architect enforces serialized editing of Version Controlled Packages, using the lock-modify-unlock mode of operation.
|Version Control Basics
Applying Version Control to Models
Using Version Control consists of placing individual model Packages under Version Control, rather than Version Controlling the project as a whole.
|Version Control Of Model Data Version Control Nested Packages
Version Control and Project Reference Data
To share changes in reference data between users in a version-controlled project deployed as multiple private models, you periodically export the reference data from the model where the changes were made, and import it into the other models maintained by the team.
|Version Control and Reference Data
Offline Version Control
You can prevent the system 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.
|Offline Version Control
- Packages under Version Control are identified in the Project Browser by icons that indicate the current status of the Package