In the relevant Workspace, combine all completed Change Sets that are not in the latest baseline. Resolve any conflicting versions of the artifacts by either removing one of the change sets that created the conflict or by creating a new change set that includes merged versions of the conflicting artifacts.

Create the build. The details of this step depend upon the implementation language and development environment and may involve compiling and linking (in the case of compiled languages) and/or other processes that result in an executable increment of the system.

Examples of these steps include:

1. Compiling and linking the source artifacts to create an executable
2. Loading binary objects on a test bench or simulator
3. Running a script to load/update database schemas
4. Packaging and deploying web applications
   

Re-run the developer tests against the integrated elements to verify that they behave the same as they did in isolation. Ensure that the scope of these tests is as broad as possible, which ensures that the latest change sets did not cause failing developer tests in other areas of the system.

Several builds will be created in each iteration. For each build, this step is performed only when change sets have been delivered to satisfy the requirements of that build.

Execute a sub-set of the system tests to ensure that the build is suitable prior to committing resources to the full scope of system testing. While the level of testing will vary, focus on gaining confidence that the increment is of sufficient quality to establish a baseline for system testing.

When tests are successfully completed and the build is considered "good," the results are made available to the rest of the team by Promoting Changes. The details of this step depend on the configuration management tools in use, but in general this involves committing a tested change set to the CM repository so that it serves as the basis of development for the next increment of the system.  This is the essence of Continuous Integration.