Use the Git source configuration type (SCT) to load artifacts from a Git repository. The Git SCT is implemented as an external type.
To set Git as an artifact source, select Git from the Source Config Type list and then specify its properties. For details about creating components, see Create components.
Git SCT settings
The following table describes the properties specific to the Git source configuration type:
|Repository URL||Enter the base URL for the Git repository.|
|Branch||Enter the Git branch from which to get artifacts, such as main.|
|Watch for tags||If selected, Deployment Automation watches for new tags instead of new versions.|
|Includes||The patterns to match files to upload. The wildcard ** indicates every directory, and the wildcard * indicates every file. For example, dist/**/* retrieves the entire file tree under the dist directory.|
|Excludes||The patterns to match files to exclude from the upload.|
Enter the Git client executable, using the full path if necessary. For example:
|Preserve Execute Permissions||(Optional) Select this option to save file execute permissions along with the files.|
|Use Latest Component Properties for Version Download||
(Optional) Select this option if you want Deployment Automation to use the current component properties instead of the properties that are set when the version is created.
Note: Component version properties are always preserved when a version is created.
|Copy to CodeStation||
(Optional) Use this option to create a tamper-proof copy of the artifacts and store them in the DA's embedded repository, CodeStation.
For optimal use of Deployment Automation, we recommend that this option is selected.
Clear the option to save pointers to versions rather than the versions themselves. This way, you can track versions and save space on your Deployment Automation server, but this limits your ability to download individual versions.
For details on maintaining versions in external sources, see CodeStation: maintain versions externally.