...
The Attributes are optional data that you can use to give different values to executions based on which branch you built from.
...
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.
...
Field Name | Required | Description |
|---|---|---|
SVN Instance | Yes | An SCM Instance representing a Subversion repository. See Instances section of this guide to create SCM Type Instance. Refer to the SCM Instances page for more information. |
Trunk Path Script | Yes | Path for the trunk within selected repository. |
Branch Path Script | No | Path for the branches within selected repository. Use the BranchName variable to identify branch name used at runtime. |
Tag Path Script | No | Path for the tag within the selected repository. Use the ProjectVersion variable to specify identifier of current build. |
Checkout Folder Script | No | Optional sub-folder to use for export/checkout operations during build workflow execution. |
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.
...
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. Multiple folders can be 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. |
Advanced Git Integration
| Info |
|---|
Prerequisites This feature is available only if your FlexDeploy instance has a configured System Integration and you have authorized your FlexDeploy user profile. See the OAuth documentation for more information. |
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.
...
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.You can change what branch you are viewing the contents for with this dropdown.
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.
1. Creating the remote Branch when a FlexDeploy Branch is created
...
2. Delete the remote branch when a FlexDeploy Branch is deleted.
...
3. Lastly, you can import several remote branches at once by clicking the Import From Remote button next to the Branch Create button. Here you can pick and choose from a list of remote Branches that should be created in FlexDeploy.
...
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.
...
Field Name | Required | Description |
|---|---|---|
CVS Instance | Yes | An SCM Instance representing a CVS repository. See the Instances section to create SCM Type Instance. Refer to the SCM Instances page for more information. |
Module Names Script | Yes | Module Names or Module subdirectories to be selected from repository. Module subdirectories should traverse starting at the Module Name. Multiple Modules may be selected by separating the names/paths with commas. |
Branch Name Script | Yes | Path for the branches within selected repository. Use BranchName variable to identify branch name used at runtime. |
Tag Script | Yes | Tag script to be used when creating tags for the project in the repository. Use ProjectVersion variable to specify identifier of current build. |
Checkout Folder Script | No | Optional sub-folder to use for clone operation during build workflow execution. |
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.
...
Field Name | Required | Description |
|---|---|---|
TFVC Instance | Yes | An SCM Instance representing a TFVC repository. See the Instances section to create SCM Type Instance. Refer to the SCM Instances page for more information. |
Main Path Script | Yes | Main Path to a project in the selected repository. |
Branch Path Script | Yes | Path for the branches within selected repository. Use BranchName variable to identify branch name used at runtime. |
Label Name Script | Yes | Label script to be used when creating labels for the project in the repository. Use ProjectVersion variable to specify identifier of current build. |
Get Folder Script | No | Optional sub-folder to use for clone operation during build workflow execution. |
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.
...