Source Configuration Type Fields

The Source Config Type field enables you to select a built-in or custom source configuration type. This enables you to load or point to artifacts stored in external tools or locations into Deployment Automation as component versions.

Loading artifacts into Deployment Automation enables you to track your artifacts as component versions as they are deployed into application environments.

Note: The source configuration types are not the same as plugins. Plugins are special integrations used in processes. For details on using plugins, see Component Processes and the Deployment Automation Plugins Guide.

Depending on the Source Config Type you select, various tool-specific fields appear. Point to the question mark ( ? ) after a field to view a description of the field.

Select None if you don't want to put artifacts into Deployment Automation. You might decide to do this if you are using another product for the deployment activities, such as Dimensions CM, and using Deployment Automation only for further configuration and processing post-deployment. If you use None, you may not have visibility into artifacts' associated component versions within Deployment Automation application environments, and would need to rely on the other product for that information.

The source configuration tools that you can select are shown in the following table.

Source Config Type	Description
AnthillPro	Select this to load artifacts that are stored in AnthillPro into Deployment Automation as component versions.
Artifactory - Folder based	Select this to load artifacts that are stored in file folders managed by Artifactory into Deployment Automation as component versions.
Artifactory - Maven / NuGet	Select this to load artifacts that are stored in Maven or NuGet repositories that are managed by Artifactory into Deployment Automation as component versions.
ClearCaseUCM	Select this to load artifacts that are stored in ClearCase UCM into Deployment Automation as component versions.
Dimensions	Select this to load artifacts that are stored in Dimensions CM into Deployment Automation as component versions.
File System (Basic)	Select this to load 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.
File System (Versioned)	Select this to load artifacts into Deployment Automation from directories in your file system, creating a component version for each subdirectory in the base path.
Git	Select this to load artifacts that are stored in Git into Deployment Automation as component versions.
Jenkins	Select this to load artifacts that are stored in 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.
Luntbuild	Select this to load artifacts that are stored in Luntbuild into Deployment Automation as component versions.
Maven	Select this to load artifacts that are stored in Maven into Deployment Automation as component versions.
Nexus	Select this to load artifacts that are stored in Nexus into Deployment Automation as component versions.
PVCS	Select this to load artifacts that are stored in PVCS into Deployment Automation as component versions.
Perforce	Select this to load artifacts that are stored in a Perforce versioning engine into Deployment Automation as component versions.
StarTeam	Select this to load artifacts that are stored in Borland StarTeam into Deployment Automation as component versions.
Subversion	Select this to load artifacts that are stored in Subversion into Deployment Automation as component versions.
TFS	Select this to load artifacts that are stored in Microsoft Team Foundation Server (TFS) into Deployment Automation as component versions. Use this if using XAML build automation.
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.
TFS_SCM	Select this to load artifacts that are stored in TFS_SCM into Deployment Automation as component versions.
TeamCity	Select this to load artifacts that are stored in JetBrains TeamCity into Deployment Automation as component versions.
TeamForge	Select this to load artifacts that are stored in CollabNet TeamForge into Deployment Automation as component versions.

For information on some of the source configuration types' fields, see the following topics.