Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Contents |
Prev | Next |
Version Control Product Setup
To control and maintain the different revisions of your project Packages, Enterprise Architect uses third-party version control products. Once your version control product is installed and a suitable environment has been created, Enterprise Architect can use that environment to control your project's Packages.
Typically, version control products consist of:
Enterprise Architect integrates with the version control client components for Subversion, CVS and MS Team Foundation Server command line clients, as well as for products having API clients that comply with the MS SCCI specification.
Version Control System Components
Component |
Detail |
See also |
---|---|---|
Version Control Server |
The server component maintains the controlled files in their many revisions, in a central repository. The server component is usually located on a server machine that is accessible to all team members who are using version control. |
|
Server Configuration |
The steps for configuring a version control server are, broadly:
For details on configuring any particular version control server, consult the appropriate documentation provided with the version control product. |
|
Version Control Client |
The client component manages the working copies of the controlled files, submitting files to or retrieving files from the server as required. A version control client must be installed on every machine on which you run Enterprise Architect and want to access your version control system. |
|
Client Configuration |
The steps for configuring a version control client are, broadly:
For details on setting up a product-specific version control environment for use with Enterprise Architect, click on the appropriate link in the next column. |
Create an SCC Environment Create a CVS Environment Create a Subversion Environment Create a TFS Environment |