Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Create a CVS Environment
You can use Concurrent Versions System (CVS) as a version control provider for Enterprise Architect. The first step in doing this is for a CVS administrator to install and configure the appropriate software. A number of basic tasks are performed in creating an operational CVS environment, and useful tools are available for performing some of these tasks.
Tasks in Creating a CVS Environment
Task |
Detail |
See also |
|---|---|---|
|
Install server components |
Executable files for CVS can be obtained from March Hare Software. CVS server components are available to run on a wide range of different hardware and operating systems; Enterprise Architect is not affected by your choice of server components. |
CVS Documentation CVS Repository Administration March Hare CVS |
|
Create a repository |
Please consult the official CVS documentation. |
|
|
Create CVS users |
Please consult the official CVS documentation. |
|
|
Create a new repository module |
It is recommended good practice to create a new repository module in CVS for each new Enterprise Architect model being added to version control with CVS. Users should create a new local working copy folder from the module to be used with that model. A repository module represents a project, or a set of related files in the repository. TortoiseCVS can greatly simplify the process of creating new repository sub-trees. |
TortoiseCVS CVS Starting a New Project |
|
Install client components |
Executable files for CVS can be obtained from March Hare Software. Enterprise Architect is a Windows based application - it requires a Windows based CVS command line client for integration. |
March Hare CVS |
|
Create a working copy folder |
A working copy folder must exist on each users' machine, for Enterprise Architect to use when exporting and importing the version controlled Package files. It is this folder that is specified as the Local Project Path, when defining your Version Control Configurations. The working copy folder is the 'sandbox' where you modify the controlled files. The working copy folder is usually associated with a folder that exists within the version control repository. In CVS, to create a local working copy you perform an initial check-out of a folder from the CVS repository; this downloads a copy of the folder and its contents, to create your local working copy. TortoiseCVS can greatly simplify the initial check out of a working copy folder. |
Prepare a CVS Local Workspace TortoiseCVS |
|
Setting up CVS under Wine/CrossOver |
The process of setting up and using CVS with Enterprise Architect under Wine is almost identical to the process when running natively under Windows, apart from minor differences in installing the CVS client and performing the initial checkout of the working copy folder. |
Notes
- If you do not already use CVS for version control, you should consider using Subversion instead; Subversion's client-server protocols provide a broader range of possibilities for connecting to remote servers, with easier set up of secure connections
- TortoiseCVS is a Windows shell extension; Enterprise Architect cannot use TortoiseCVS as its client, it must use the CVS command line client
Learn more
