Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Version Control Product Setup
Enterprise Architect relies on third-party version control products to control and maintain the different revisions of your project packages.
Once your version control product is installed and a suitable environment has been created, Enterprise Architect can then utilize that environment to control your project's packages.
Guide:
Topic |
Detail |
See also |
||||||||
---|---|---|---|---|---|---|---|---|---|---|
Version Control System Components |
Typically, version control products consist of:
Enterprise Architect integrates with version control client components. It provides integration for Subversion, CVS and MS Team Foundation Server command line clients, as well as integration for products having API clients that comply with the MS SCCI specification.
|
|
||||||||
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 by all team members who are using version control.
|
|
||||||||
Server Configuration |
Steps involved in configuring a version control server usually include:
The details of configuring any particular version control server are beyond the scope of this document. Please consult the appropriate documentation.
|
|
||||||||
Version Control Client |
The client component deals with the working copies of the controlled files, submitting or retrieving files to and from the server as required. A version control client must be installed on every machine where you run Enterprise Architect and want to access your version control system.
|
|
||||||||
Client Configuration |
Steps involved in configuring a version control client usually include:
For specific information on how to set up a version control environment for use with Enterprise Architect, follow the appropriate link at right.
|