Jazz includes the Jazz Build Engine and an Ant build toolkit that can publish build information to the Jazz repository. While the build toolkit is best suited for Ant builds, you can use any scripting technology that can invoke Ant. For example, a team can use Perl, DOS batch files, or Make, to create build scripts that interact with Jazz Team Build.
All build-related items belong to a project area. Build-related operations are governed by the project's process.
Jazz builds can have traceability between change sets and work items. You typically run a build against files that come from a designated build repository workspace that has incoming flows from the team's main development stream.
Before running the build, all the latest changes are accepted from the team's stream and a reproducible snapshot of the files is created. The change sets and work items included in the build are recorded for consumers of the build to view.
After a build is considered good, you can create a Release from the build. You can then set the Found In field of a work item to the particular release associated with the build.
The following figure illustrates the traceability between change sets and work items when you run a build against files from a team stream.
