Branch Project: Version Control Settings

The Version Control Settings page in the Branch Project wizard configures one or more Source Control Management (SCM) instances, enabling the branching process to synchronize the branched project with remote codebase repositories in your site’s SCM applications. The synchronization takes place once the branching process begins. For more information about how to set up for SCM synchronization and how the synchronization process works, refer to Configuring Source Code Management.

By default, any SCM instances used by the source project are automatically copied to this page, each instance defined on a separate tab. However, you can edit or remove any of these instances or add new ones for the branched project. Alternatively, you can choose not to include any SCM instances on the Version Control Settings page, but can always return to this page to add instances later during setup if you want.

This page is enabled only if you selected the Sync from Source Control option from the previous Project Information page.

If you also uploaded codebases from the Upload Codebase page, the codebase files obtained through SCM synchronization, as defined on this page, will be added to the uploaded codebase files to provide the complete codebase for the branch product.

For a description of the procedures related to the Version Control Settings page, see the following:

•

Branching a Project

•

Step 3: Configuring Synchronization with a Source Code Management Instance (Optional)

The following describes the properties and actions available on the Version Control Settings page:

Branch Project: Version Control Settings

Field		Description
Add Instance	Click this button to create a new instance to connect to and synchronize with a remote SCM repository.
Application	Select the type of SCM application to which the remote repository belongs: Git, Perforce, or TFC (Team Foundation Server).
Instance tab	If the source project contains SCM instances, these are copied to the branched project, each on a separate tab. Additionally, a new tab is created for each new SCM instance you decide to set up. The following provides information about the properties required for each instance and the actions you can perform on the instance.
	Instance properties	Provide or edit the properties for the new or existing SCM connection instance. Click the appropriate link below for a description of the properties used to configure an instance based on the SCM application type. • Git instance—Refer to Configuring an SCM Git Instance. • Perforce instance—Refer to Configuring an SCM Perforce Instance. • TFS instance—Refer Configuring an SCM TFS Instance.
	Test Connection	To ensure that Code Insight is able to connect to the remote SCM repository specified by the instance, click this button. After a moment, Code Insight displays a success message if the connection is made. If the connection is not successful, ensure that your entries on the Instance tab are correct, and click Test Connection again.
	Delete Connection	Click this button to permanently remove this instance from the branched project (and thus from the Code Insight system). Keep in mind that, if this instance was copied from the source project and you delete it here, the branch might no longer contain the same codebase files as the source project.
Next	Click this button to perform a final “test connection” on each connection instance incrementally. If all connections are successful, the Project Copy Settings page in the wizard is opened. If a connection to a given repository fails, an error message is displayed, specifying which connection instance has failed. You must correct all connection issues before proceeding with the project-branching setup.
Back	Click this button to move to the previous wizard page. Note that if you navigate back to the Project Information page, you cannot edit the Name field for project. Additionally, if you uploaded a codebase from the Upload Codebase page, the Scan Server and Upload Codebase options on the Project Information page are disabled.
Cancel	Click this button to cancel the project-branching setup. The branched project and any uploaded codebases for the project are deleted from Code Insight.