Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Applying Version Control in a Team Environment
The following information provides an overview of 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.
Use to
| • | Setup a version control environment |
| • | Apply version control to an Enterprise Architect project |
How to
Step |
Action |
See also |
||||
1 |
Install your version control product.
|
|
||||
2 |
Create a version control repository.
|
|
||||
3 |
Create a version control project to be used with your Enterprise Architect project.
|
|
||||
4 |
Check-out a working copy of the version control project (a module, project or folder within the version control system) into a local folder. (You must do this for every team member that is accessing the version controlled packages, whether you are using a single shared model or each team member stores his own private copy of the model.)
|
|||||
5 |
Within Enterprise Architect, define a version control configuration to provide access to the working copy files. Throughout a team, the name of the version control configuration must be the same across all machines. That is, all version control access to a given Enterprise Architect package must be through version control configurations with the same name, across all models and all users. The easiest way to perform this step, (throughout the team), is to have one user set up version control on the model and then share that model with the rest of the team.
Whenever you open a model (Private or Shared) that uses a version control configuration that is not yet defined on your workstation, Enterprise Architect prompts you to complete the definition for that configuration. This typically means specifying the local working copy directory and maybe choosing the version control project associated with this Enterprise Architect project. Once this has been done, the version controlled packages that already exist in the model are ready for use.
|
|||||
6 |
Configure packages within the Enterprise Architect model for version control. That is, apply version control to individual packages.
|
|||||
7 |
Check-out and check-in packages as required. |
|
Notes
| • | It is possible to use multiple version control configurations within the same model, so different packages can still use different version control configurations within the same model, as long as any given package is always accessed via the same version control configuration |
Learn more
Team deployment and the use of version control is discussed in two Sparx Systems white papers, available on the Sparx Systems web site:
