Source Configuration Type Fields

The source config type field enables you to select a product from which you want to load artifacts into Deployment Automation as component versions. Deployment Automation integrates with the source configuration tools to provide this functionality. Loading artifacts into Deployment Automation enables you to track your artifacts as component versions as they are deployed into application environments.

Note: The Source Config Type integrations are not the same as plug-ins. Plug-ins are special integrations used in processes. For details on using plug-ins, see Component Processes and the Serena Deployment Automation Plug-ins Guide.

Depending on the Source Config Type you select, various tool-specific fields appear. For information on each source configuration type's fields, in the web application user interface, click the ? icons next to fields.

For information on the versions of these tools supported by the source configuration integration, see the Platform Matrix link for your version of Release Manager on the Serena Support product download page.

The source configuration tools that you can select include the following:

Source Config Type	Description
None	Select None when 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 will 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.
AnthillPro	Select this to load artifacts that are stored in AnthillPro into Deployment Automation as component versions. See AnthillPro.
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.
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.
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 plug-in 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.
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. See TFS.
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.
TeamForge	Select this to load artifacts that are stored in CollabNet TeamForge into Deployment Automation as component versions. See TeamForge.
uBuild	Select this to load artifacts that are stored in uBuild into Deployment Automation as component versions.