Add a build source

You can configure a build source for "build" steps in your pipeline.

1. Click the project name in the breadcrumb navigation.
2. Click Edit for your pipeline. If your pipeline has:
   • No steps — You see the "Manage Pipeline" page. Add one or more build steps for your pipeline, then click on Save and Add Sources to navigate to the "Manage Sources" page.
   • One or more steps — You see the "Manage Sources" page. If you have one or more build steps in your pipeline, you can now add or edit sources for your build steps. If you have no build steps, click Manage Pipeline. On the "Manage Pipeline" page, add one or more build steps for your pipeline and then click on Save and Add Sources to navigate to the "Manage Sources" page.
3. Select the "build" step that you want to configure. TeamForge Orchestrate displays all the defined sources for a step, in the order in which they were defined.

You can choose to edit an existing source, or create a new source for this pipeline step.

4. 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 an SCM 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 an SCM source. See Adding an SCM source for information about adding a commit source if none are available for selection.
   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.
5. To create a new build source, click Add a new source.
   1. Provide a display name for the build source that is depicted on all screens in the TeamForge Orchestrate user interface. The display name can be up to 100 alphanumeric characters in length.
   2. Select a commit source: Select the SCM source from the list of existing SCM sources for your pipeline. In order that TeamForge Orchestrate create associations between your build and commit activities, you must select an SCM source from the list of existing SCM sources for your pipeline.

      If you do not select an SCM 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 an SCM source. See Adding an SCM source for information about adding a commit source if none are available for selection.

      For most source types, TeamForge Orchestrate generates a unique "source association key". The source association key uniquely identifies and helps route data from sources to the proper source/step/pipeline in TeamForge Orchestrate. You must supply this string while configuring adapters for SCM, build and review services. You can copy the key by clicking on the small clipboard icon. No association key is necessary when you configure a TeamForge project repository, though.

6. Click Done.

   TeamForge Orchestrate saves the new build source, and activates it.