Configuring Git Version Control for Model Repository Service in 10.2 HotFix 1

Configuring Git Version Control for Model Repository Service in 10.2 HotFix 1

Overview

Overview

You can integrate a Model Repository Service with a version control system, such as Perforce, Subversion, or Git system. Git is a distributed version control system.
A version control system allows one user at a time to check out, edit, and save an object. When you save an object, the object is saved in the Model repository. After you check in the object, a version is created in the version control system. The version control system maintains a history of all the versions. You can edit only the latest version of the object. You can view the other versions of the object in read-only mode. You can roll back to a previous version or reassign the checked-out state of objects to another user. A version control system protects a Model repository object from unwanted updates because it does not allow multiple users to edit an object at once.
To integrate the Model Repository Service with Git version control system, you can configure the versioning properties of the Model Repository Service. Then, set the
git_local_repository_path
custom property with the file path of the local Git repository, and recycle the Model Repository Service.
When you choose the Git version control system, you can configure the following components:
Remote Git repository
You need access to the remote repository on the Git server. To configure the version control system, you need the URL, user name, and password of the remote repository. You can use HTTP or HTTPS protocol to access the remote Git repository.
Local Git repository
Create a directory on the machine that hosts the Model Repository Service to serve as the local Git repository.
The directory must meet the following requirements:
  • Access to all the client machines.
  • Access to the backup nodes for the Model Repository Service after you enable high availability.
  • Support for NFS, FAT32, and NTFS file systems.
  • Have a unique name.
  • Have read, write, and execute permissions.
When you check in an object, the Git version control system checks in the object. It saves a copy in the remote Git repository and local Git repository. If the remote Git repository is inaccessible or if it shuts down unexpectedly, you can access the local Git repository to view all the versions and edit the latest version of the object.


Updated October 24, 2019