...
Defaults for Subversion source configurations can be configured using Project SVN Setup Defaults. This can be configured such that
All Subversion project sources will get same values (including SVN Instance), or
you can configure defaults by SVN Instance.
First approach works well if you have a single Subversion repository. If you have multiple Subversion repositories in your environment, then you can utilize second approach to configure project based on some criteria. You can accomplish this by placing an "if" statement within Groovy script for the defaults. With this approach all attributes in Subversion configurations will be empty initially, and when user selects SVN Instance, configuration values will be defaulted appropriately.
...
Defaults for Git source configurations can be configured using Project GIT Setup Defaults. This can be configured such that
All Git project sources will get same values (including Git Instance), or
You can configure defaults by Git Instance. First approach works well if you have a single Git repository.
If you have multiple Git repositories in your environment, then you can utilize the second approach to configure the project based on some criteria. You can accomplish this by placing an "if" statement within Groovy script for the defaults. With this approach all attributes in Git configurations will be empty initially, and when user selects Git Instance, configuration values will be defaulted appropriately.
...
Field Name | Required | Description |
|---|---|---|
Git Instance | Yes | An SCM Instance representing a Git repository. See the Instances section to create SCM Type Instance. Refer to the SCM Instances page for more information. |
Branch Name Script | Yes | Path for the branches within selected repository. Use BranchName variable to identify branch name used at runtime. |
Tag Name Script | Yes | Path for the tag within the selected repository. Use ProjectVersion variable to specify identifier of current build. |
Sparse Checkout Folders Script | No | This is very useful when you have many folders in your Git repository, but your project only needs few folders for build. This Multiple folders can be specified as one more values by using comma. For example, HRDemoApp, which will only pull HRDemoApp from Git repository. separated by commas. Continuous integration support will make sure to check for changes only in these folders as well if configured. e.g. “HRDemoApp” -only pull HRDemoApp from Git repository. e.g. “HRDemoApp,ConfigPlans” -only pull folders HRDemoApp and ConfigPlans (and their contents) from Git repository. |
Checkout Folder Script | No | Optional sub-folder to use for clone operation during build workflow execution. |
...
Defaults for CVS source configurations can be configured using Project CVS Setup Defaults. This can be configured such that
All CVS project sources will get same values (including CVS Instance), or
You can configure defaults by CVS Instance. First approach works well if you have a single CVS repository.
If you have multiple CVS repositories in your environment, then you can utilize the second approach to configure the project based on some criteria. You can accomplish this by placing an "if" statement within Groovy script for the defaults. With this approach all attributes in CVS configurations will be empty initially, and when user selects CVS Instance, configuration values will be defaulted appropriately.
...
Defaults for TFVC source configurations can be configured using Project TFVC Setup Defaults. This can be configured such that
All TFVC project sources will get same values (including TFVC Instance), or
You can configure defaults by TFVC Instance. First approach works well if you have a single TFVC repository.
If you have multiple TFVC repositories in your environment, then you can utilize the second approach to configure the project based on some criteria. You can accomplish this by placing an "if" statement within Groovy script for the defaults. With this approach all attributes in TFVC configurations will be empty initially, and when user selects TFVC Instance, configuration values will be defaulted appropriately.
...
Defaults for PVCS source configurations can be configured using Project PVCS Setup Defaults. This can be configured such that
All PVCS project sources will get same values (including PVCS Instance), or
You can configure defaults by PVCS Instance. First approach works well if you have a single PVCS repository.
If you have multiple PVCS repositories in your environment, then you can utilize the second approach to configure the project based on some criteria. You can accomplish this by placing an "if" statement within Groovy script for the defaults. With this approach all attributes in PVCS configurations will be empty initially, and when user selects PVCS Instance, configuration values will be defaulted appropriately.
...