Integration → Source Configuration Tools
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.
The source configuration tools that you can select include the following:
| Source Config Type | Description |
|---|---|
| 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. |
Copyright © 2011–2015 Serena Software, Inc. All rights reserved.