Manage build source

Add build sources to bring automated build job results into the TeamForge project and traceability context.

Build sources bring build/CI data into Orchestrate for archival of meta data, participation in traceability, and activity reporting. This document describes the process to add a new build source.

From the activity stream, click Manage Sources.
Select the Build toggle. TeamForge Orchestrate displays all existing "build" sources.

You can choose to edit an existing source, or create a new build source.

To edit an existing build source, click Edit. You can edit the display name or associate a different commit source for this build source. If you do not select a commit source, no associations will be drawn for the build activities coming from this build source. TeamForge Orchestrate displays a warning if a build source is not associated with a commit source. See Manage commit sources.
Note: While editing an existing source configuration, you can click DEACTIVATE to stop TeamForge Orchestrate from collecting data from that source; click ACTIVATE to resume data collection from the source.
To create a new build source, click Add a new source.
1. Provide a display name for the build source. This display name will appear throughout the TeamForge Orchestrate user interface. The display name can be up to 100 alphanumeric characters in length.
2. Select a commit source: Select the commit source from the list of existing commit sources (or create a new one). In order that TeamForge Orchestrate create associations between your build and commit activities, you must select a commit source from the list of existing commit sources.
  If you do not select a commit source, no associations will be drawn for the build activities coming from this build source. TeamForge Orchestrate displays a warning if a build source is not associated with a commit source. See Manage commit sources for information about adding a commit source.
  
  For most source types, TeamForge Orchestrate generates a unique "source association key". The source association key uniquely identifies and helps route data from sources properly in TeamForge Orchestrate. You must supply this string while configuring adapters for most source types. You can copy the key by clicking on the small clipboard icon. No association key is necessary when you configure a TeamForge project code repository, though.
Click Done.
TeamForge Orchestrate saves the new build source and activates it.