TeamForge Orchestrate pipeline steps include commit, build, and review activities. You can configure activities so that they are triggered automatically on events such as new commits.
A pipeline is composed of user-configurable steps. Steps are activities like commits, builds, and code reviews. Each step may contain one or more sources of data, for example, multiple source control servers or build servers.
When TeamForge Orchestrate detects a new commit from a pipeline's SCM repository, it triggers the subsequent build step. If that step contains multiple sources, TeamForge Orchestrate triggers a build on each source. This can be used as an alternative to having the build server poll the SCM server directly.
When TeamForge Orchestrate detects a new build from a pipeline's build server, it triggers the subsequent build step. If that step contains multiple sources, TeamForge Orchestrate triggers a build on each source. This allows you to configure TeamForge Orchestrate to manage multiple-step builds. For example, suppose a commit triggers a build step that runs unit tests. When that step completes, integration and performance tests can be automatically triggered.