You can integrate a Model repository with a version control system. Version control system integration protects Model repository objects from overwriting on a team where multiple developers work on the same projects.
To enable version control, configure versioning properties, and then synchronize the Model repository with the version control system.
You can integrate the Model repository with the Perforce or Subversion version control systems. You must use a version control system that has not been integrated with a Model repository. Only one Model repository can use a version control system instance.
You can configure versioning properties when you create or update a Model repository service.
The versioning properties include a version control system user ID and password. The connection uses this single account to access the version control system for all actions related to versioned object management.
After you configure version control, ask Model repository users to close all editable objects, and then you restart the Model repository.
When the Model repository restarts, it checks whether the version control system is in use by another Model repository. If the version control system connects to a different Model repository, the Model Repository Service cannot restart. You must configure versioning properties to connect to a version control system that has not been integrated with a Model repository.
When you synchronize Model repository contents to the version control system, the Model repository populates a directory in the version control system depot with Model repository objects. After the Model repository copies its contents to the version control system directory, you cannot disable version control system integration.
When the Model repository is integrated with a version control system, you can perform the following tasks:
Check in revised objects.
Undo the checkout of objects.
Reassign the checked-out state of objects to another user.