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.
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
To create an SCM Instance, select the Source Control tab, and click the Create button in the top right of the table. To edit an existing Instance, click on an Instance’s name in the table. A popup will open.
...
Enter values for the fields as described in figure below.
...
Field Name | Required | Description | ||
|---|---|---|---|---|
Instance Name | Yes | Long display name for the Instance. | ||
Instance Code | Yes | Short name for the Instance. | ||
SCM Type | Yes | Once the SCM Instance is saved, this field cannot be modified. | ||
Description | No | 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 once selected in the dropdown. Alternatively, you can reuse a single credential for multiple properties also, in which case you should name that credential appropriately. |
...