Tip: Add and edit branches using the ALI Configuration wizard while configuring a related build job (recommended), or manually as described below.
If you are configuring branches manually, it is still recommended to start by configuring a related build job, as described in Add and edit build configurations.
![]() |
Select a system type to filter the descriptions below. |
The following information is customized according to your selections. Check that your selections are correct.
If any selections are not correct, click Change.
Do one of the following:
To add a new branch: Select a repository, and click Add SCM Branch.
To edit a branch: Expand a repository, and click a branch.
On the SCM Branch page, set the following branch properties:
Set the branch path without the Depot name. For example, if the branch is located at //depot/HelloWorld/releases/release-1.0/..
. then the path should be /HelloWorld/releases/release-1.0
.
Use the branch path to the project path without $
. For example, if the project is located at $/TestApp
, then the branch path should be /TestApp
. The branch path must contain only the name of the project. Paths containing subfolders are not supported.
Always set the branch path to /
.The field name should be set to the real Git branch name.
A branch name only has meaning for some CVS repositories. Do not fill this property for SVN.
Do not use this field even if the branch is named.
Use only the simple branch name in the format master
, and not refs/head/master
.
The date-time stamp for which the change sets are read.
Note: Populate this field when creating a new branch to read changes only starting from branch creation. Leaving this field blank will include all changes starting from the beginning of the master/HEAD branch.
The last revision number for which change sets are read.
Note: Populate this field when creating a new branch to read changes only starting from branch creation. Leaving this field blank will include all changes starting from the beginning of the master/HEAD branch.
The commit hash (revision), space, and branch name. For example:
Master | 00988ff4a833eea670feab6bcbcf5ed93f9add77 master
|
|
A branch named 2.10 | a12a5d41b0fba9934e9569cbae87e61599373ea2 2.10
|
Note: Populate this field when creating a new branch to read changes only starting from branch creation. Leaving this field blank will include all changes starting from the beginning of the master/HEAD branch.
Note:
Disallow commits except for the following. disallows all the commits coming to the given branch other than the following exceptions:
A list of users allowed to commit to the branch can be specified though the branch is locked by applying the user name(s) of SCM users who are permitted to commit.
A list of defects specified for which committing changes are allowed is created by clicking Add and providing the ID of the defect. Defects are removed from the table by clicking Remove.
Note:
You can associate a branch with multiple releases. Click Add and select the releases.
The start and end dates of the releases are taken from the release settings. You can change these manually in the grid.
Change sets from the branch are associated with a release during the time period specified for that release.
Select the application with which the branch is associated.
Note: After filling these fields, click Validate Configuration to test the settings.