TeamForge Orchestrate creates associations between activities such as reviews, commits, builds, and work items.
Most associations in TeamForge Orchestrate center around commits. That is, builds, work items, and reviews associate directly to commits, while a build-to-review association are implied through a common commit.
Builds are associated to commits by the underlying CI/build system. Typically, CI/build systems obtain source code from a target repository and build based on that specific revision of source code. TeamForge Orchestrate therefore relies on the CI/build system to report the associated revisions, which then get mapped as associations between commits and builds in TeamForge Orchestrate.
Reviews associate to commits in one of two ways, depending on the process being employeed and the source code review product. Please see Review detail for a detailed explanation on commit-to-review associations.
When creating code reviews, note that the code review's repository URL must match the one specified while configuring the related SCM source. Otherwise, TeamForge Orchestrate will not be able to register associations between commits and reviews.
Work items can be directly associated to commits by referencing the work item artifact ID in the commit message. Please see Work item detail for a detailed explanation on commit-to-work-item associations.