SCM Instance is configuration details to connect with specific code repositories like GitHub, GitLab, Subversion etc. This information is used to check for changes in repository. Plugins can use the details to checkout, commit code as well.
To create an SCM instanceInstance, click the Create button and select SCM Instanceselect the Source Control tab, and click the
button. To edit an existing instanceInstance, select an instance and click the Edit button. click on an Instance row from the list.
...
Enter values for the fields as described in figure below.
Selection of the SCM type dynamically prompts for properties required to for that SCM. Clicking the Test Connection button will use the values you entered to connect to the SCM instance.
Click the Save button to save the changes.
Instance.
Field Name | Required | Description |
|---|---|---|
Instance Code | Yes | Short name for the |
Instance. | ||
Instance Name | Yes | Long display name for the |
Instance. | |
SCM Type | Yes |
Once the SCM Instance is saved, this |
field cannot be modified. | ||
Description | Yes | A description of the |
Instance. | ||
Active | Yes | Whether or not the |
Instance is active in the system. Defaults to "Yes". | ||
URL | Depends | URL to the repository |
If using SVN,
If using PVCS, This will be the Project Database client name configured on the FileServer. e.g. /opt/pdb/pdbname | ||
User | Depends | User name to login to the repository. |
Password | Depends | Password to login to the repository. Note that encrypted properties are stored in Credential Store (Local or External) and can be configured using Edit button next to credential name drop down. Alternatively, you can reuse single credential for multiple properties also, in which case you should name that credential appropriately. |
Click the Save button to save the changes. Optionally click the Apply button to save the changes, but remain on the current screen until the Cancel button is clicked.