Select Projects from the menu.

Open an existing project and click on Configuration, Source Control tab.

Source Configuration

Source configuration is is selecting the SCM Type and repositories for the project.

Open

Clicking Advanced allows for further configuration.

The inputs are in Groovy format, so you can use some variables in them. Static values should be quoted. Pressing Ctrl+Space shows different variables that are available.

Branch Configuration

Branch configuration is how you setup different copies of the same files in your source control system.

One branch is tagged as Main. This branch is the default branch to build from.

The Version Name Syntax input helps you to create a unique version identifier from each build.

The Next Branch Build Number increments with each build.

The Attributes are optional data that you can use to give different values to executions based on which branch you built from.

Open

Subversion Source Configurations

For Subversion one or more project sources can be configured with the details as described in the table below. FlexDeploy provides flexibility by supporting groovy script to define these values. Click on the expression button to include variables as part of the value. Additional sources can be added by Clicking on the Add Source button.

Defaults for Subversion source configurations can be configured using Project SVN Setup Defaults. This can be configured such that

1. All Subversion project sources will get same values (including SVN Instance), or

2. 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.

Git SCM Configurations

For Git one or more project sources can be configured with the details as described in table below. FlexDeploy provides flexibility by supporting groovy script to define these values. Click on expression button to include variables as part of the value. Additional sources can be added by Clicking on the Add Source button.

Defaults for Git source configurations can be configured using Project GIT Setup Defaults. This can be configured such that

1. All Git project sources will get same values (including Git Instance), or

2. 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.

Advanced Git Integration

When using Git as your source control type you can leverage several additional features that are not available for other source control types.

Browsing Sparse Folders

Rather than having to manually specify any Sparse Folders (subfolders within the Git repository that should be cloned instead of the entire repo), you can click the Magnifying Glass button next to the Sparse Folder input. This will launch a popup that allows you to select your Sparse Folders from a file browser of the repository.

1. Multiple Sparse Folders can be chosen. Here you can add additional folders by clicking the button. You can toggle which one you are currently editing with the button.

2. You can change what branch you are viewing the contents for with this dropdown.

3. Here you can choose which folder should be used as your Sparse Folder by clicking on the folder row.

Syncing Remote Branches

There 3 ways in which Branches on your remote Git repository can be synced with FlexDeploy Branches when working on the Source Control screen.

CVS SCM Configurations

For CVS one or more project sources can be configured with the details as described in table below. FlexDeploy provides flexibility by supporting groovy script to define these values. Click on expression button to include variables as part of the value. Additional sources can be added by Clicking on the Add Source button.

Defaults for CVS source configurations can be configured using Project CVS Setup Defaults. This can be configured such that

1. All CVS project sources will get same values (including CVS Instance), or

2. 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.

TFVC SCM Configurations

For TFVC one or more project sources can be configured with the details as described in table below. FlexDeploy provides flexibility by supporting groovy script to define these values. Click on expression button to include variables as part of the value. Additional sources can be added by Clicking on the Add Source button.

Defaults for TFVC source configurations can be configured using Project TFVC Setup Defaults. This can be configured such that

1. All TFVC project sources will get same values (including TFVC Instance), or

2. 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.

PVCS SCM Configurations

For PVCS one or more project sources can be configured with the details as described in table below. FlexDeploy provides flexibility by supporting groovy script to define these values. Click on expression button to include variables as part of the value. Additional sources can be added by Clicking on the Add Source button.

Defaults for PVCS source configurations can be configured using Project PVCS Setup Defaults. This can be configured such that

1. All PVCS project sources will get same values (including PVCS Instance), or

2. 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.

Click the Save button to save the changes.