Share this page
Use source configuration types
Use source configuration types (SCTs) to load artifacts from external sources into Deployment Automation as component versions. This topic describes built-in SCTs.
You can create your own SCTs. For details, see Create source configuration types.
SCT overview
Deployment Automation provides a set of built-in source configuration types (SCTs).
When artifacts are loaded into Deployment Automation, you can track them as component versions when they are deployed into application environments. Depending on the source configuration type you select, you need to specify additional tool-specific settings. To view a setting's description, hover over the field's name.
Note: Source configuration types are different from plugins. Plugins are integrations used in processes. For details, see Component plugin steps.
If you don't want to put artifacts into Deployment Automation, don't set an SCT (accept the default setting, None). If you rely on another product for deployments, such as Dimensions CM, you might use Deployment Automation only for further configuration and processing post-deployment.
If you don't set an SCT, you may not have visibility into artifacts' associated component versions in Deployment Automation application environments. And you may need to rely on other products for that information.
Built-in source configuration tools
The following table provides a list of built-in source configuration types:
| SCT | Description |
|---|---|
| AnthillPro |
Loads artifacts from AnthillPro into Deployment Automation as component versions. For details, see AnthillPro SCT. |
| Artifactory — Folder based |
Loads artifacts from file folders managed by Artifactory into Deployment Automation as component versions. For details, see Artifactory SCT. |
| Artifactory — Maven / NuGet |
Loads artifacts from Maven or NuGet repositories managed by Artifactory into Deployment Automation as component versions. For details, see Artifactory SCT. |
| ClearCaseUCM | Loads artifacts from ClearCase UCM into Deployment Automation as component versions. |
| Dimensions |
Loads artifacts from Dimensions CM into Deployment Automation as component versions. For details, see Dimensions CM SCT. |
| File System (Basic) |
Loads artifacts into Deployment Automation from directories in your file system. This imports all files in the subdirectories and creates a component version either on a designated name or based on a version name pattern. Automatic import is not supported with this option. For details, see File System (Basic) SCT. |
| File System (Versioned) |
Loads artifacts into Deployment Automation from directories in your file system, creating a component version for each subdirectory in the base path. For details, see File System (Versioned) SCT. |
| Git |
Loads artifacts from a Git repository into Deployment Automation as component versions. For details, see Git SCT. |
| Jenkins |
Loads artifacts from Jenkins into Deployment Automation as component versions. This does not display additional fields, but rather indicates that the Jenkins plugin for Deployment Automation is configured and activated. For details, see Jenkins SCT. |
| Luntbuild | Loads artifacts from Luntbuild into Deployment Automation as component versions. |
| Maven |
Loads artifacts from Maven into Deployment Automation as component versions. For details, see Maven SCT. |
| Nexus |
Loads artifacts from Nexus into Deployment Automation as component versions. For details, see Nexus Sonatype SCT. |
| PVCS |
Loads artifacts from PVCS into Deployment Automation as component versions. For details, see PVCS SCT. |
| Perforce | Loads artifacts from a Perforce versioning engine into Deployment Automation as component versions. |
| PulseUno |
Loads packages from a PulseUno vault into Deployment Automation as component versions. For details, see PulseUno SCT. |
| StarTeam | Loads artifacts from Borland StarTeam into Deployment Automation as component versions. |
| Subversion |
Loads artifacts from Subversion into Deployment Automation as component versions. For details, see Subversion SCT. |
| TFS |
Loads artifacts from Microsoft Team Foundation Server (TFS) into Deployment Automation as component versions. Use this if using XAML build automation. For details, see TFS SCT. |
| TFS vNext |
Select this to load artifacts that are stored in Microsoft Team Foundation Server (TFS) 2015 and above into Deployment Automation as component versions. If you are using XAML build automation, use the TFS source configuration type. For details, see TFS vNext SCT. |
| TFS_SCM |
Loads artifacts from TFS_SCM into Deployment Automation as component versions. For details, see TFS_SCM SCT. |
| TeamCity |
Loads artifacts from JetBrains TeamCity into Deployment Automation as component versions. For details, see TeamCity SCT. |
| TeamForge |
Loads artifacts from CollabNet TeamForge into Deployment Automation as component versions. For details, see TeamForge SCT. |
See also:
