Source configuration types

The Source Config Type field enables you to select a built-in or a custom source configuration type. This way, you can choose to use the artifacts stored in external sources and load them into Deployment Automation as component versions.

Overview

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

Note: 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, additional tool-specific fields are displayed. To view a field's description, hover over the field's name.

If you don't want to put artifacts into Deployment Automation, accept the default setting(None).

You might do this if you rely on another product for deployments, such as Dimensions CM, and use Deployment Automation only for further configuration and processing post-deployment.

If you leave the source config type set to None, you may not have visibility into artifacts' associated component versions in Deployment Automation application environments, and may need to rely on other products for that information.

Back to top

Available source configuration tools

The following table provides a list of available source configuration tools:

Source Config Type Description
AnthillPro Select this to load artifacts that are stored in AnthillPro into Deployment Automation as component versions. See AnthillPro.
Artifactory - Folder based Select this to load artifacts that are stored in file folders managed by Artifactory into Deployment Automation as component versions. See Artifactory.
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. See Artifactory.
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. See Dimensions CM.
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. See File System (Basic).
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. See File System (Versioned).
Git Select this to load artifacts that are stored in Git into Deployment Automation as component versions. See Git.
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. See Jenkins.
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. See Maven.
Nexus Select this to load artifacts that are stored in Nexus into Deployment Automation as component versions. See Nexus Sonatype.
PVCS Select this to load artifacts that are stored in PVCS into Deployment Automation as component versions. See PVCS.
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. See Subversion.
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. See TFS.
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. See TFS vNext.
TFS_SCM Select this to load artifacts that are stored in TFS_SCM into Deployment Automation as component versions. See TFS_SCM.
TeamCity Select this to load artifacts that are stored in JetBrains TeamCity into Deployment Automation as component versions. See TeamCity.
TeamForge Select this to load artifacts that are stored in CollabNet TeamForge into Deployment Automation as component versions. See TeamForge.

Back to top

See also: