Source configuration types

Deployment Automation provides a set of built-in source configuration types (SCTs), enabling you to use the artifacts stored in external sources and load them into Deployment Automation as component versions.

You can create your own source configuration types. For details, see Create custom source configuration types.

SCT overview

When artifacts are loaded into Deployment Automation, you can track them as component versions as 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 Plugin steps for component processes and Load and upgrade plugins.

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 accept the default source config type setting (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

Built-in source configuration tools

The following table provides a list of built-in source configuration tools.

Source Config Type Description
AnthillPro Loads artifacts from AnthillPro into Deployment Automation as component versions. See AnthillPro.
Artifactory — Folder based Loads artifacts from file folders managed by Artifactory into Deployment Automation as component versions. See Artifactory.
Artifactory — Maven / NuGet Loads artifacts from Maven or NuGet repositories managed by Artifactory into Deployment Automation as component versions. See Artifactory.
ClearCaseUCM Loads artifacts from ClearCase UCM into Deployment Automation as component versions.
Dimensions Loads artifacts from Dimensions CM into Deployment Automation as component versions. See Dimensions CM.
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. See File System (Basic).
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. See File System (Versioned).
Git Loads artifacts from Git into Deployment Automation as component versions. See Git.
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. See Jenkins.
Luntbuild Loads artifacts from Luntbuild into Deployment Automation as component versions.
Maven Loads artifacts from Maven into Deployment Automation as component versions. See Maven.
Nexus Loads artifacts from Nexus into Deployment Automation as component versions. See Nexus Sonatype.
PVCS Loads artifacts from PVCS into Deployment Automation as component versions. See PVCS.
Perforce Loads artifacts from a Perforce versioning engine into Deployment Automation as component versions.
StarTeam Loads artifacts from Borland StarTeam into Deployment Automation as component versions.
Subversion Loads artifacts from Subversion into Deployment Automation as component versions. See Subversion.
TFS Loads artifacts from 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 Loads artifacts from TFS_SCM into Deployment Automation as component versions. See TFS_SCM.
TeamCity Loads artifacts from JetBrains TeamCity into Deployment Automation as component versions. See TeamCity.
TeamForge Loads artifacts from CollabNet TeamForge into Deployment Automation as component versions. See TeamForge.

Back to top

See also: