|
|
|
|
|
Activity:
Start a Build (CMMI Level 3 : PI 3.2 )
|
|
Participating Roles
Responsible:
Build Engineer
Consult:
Test Manager |
Start a build whenever there is a need to integrate changes or ensure build consistency. Builds help to synchronize changes and to create a platform on which all developers can work. A build can be started manually or as a scheduled task. If the build process runs too slowly, rework dependencies to make it run more quickly.
Entry Criteria
When:
- As scheduled, or when needed.
Dependencies:
- Change Lists:
- Source Code:
- Build Type: A Visual Studio configuration file specifying the build files, dependencies, and tests to run.
Sub-Activities
|
1 |
Determine if Performance Issues Need Addressing |
- Optional
- Look for increased performance opportunities by reworking dependencies thus decreasing the time required to perform a build. Consider running builds during off-peak hours.
- Restructure components as necessary to ensure build times stay reasonable.
- Update any dependency changes resulting from new changes.
|
2 |
Initiate a Manual Build |
- Optional
- When a need to distribute changesets across the team is determined, start a manual build. Only create a clean build when absolutely necessary. A clean build occurs during the nightly build. If the build will not run unless a clean build has completed, check the dependencies to ensure that the build is running optimally.
- Coordinate with the other developers to ensure that they are not in the process of checking in development tasks. Initiate a build to allow others to use changes.
- Consider the need to run iteration tests based on the time constraints for the build. Consult with the test manager as needed.
- Be mindful of potential performance hits incurred by running builds during peak hours.
|
3 |
Initiate a Scheduled Build |
- Optional
- Start a build at a regularly scheduled interval for example, a nightly build run manually or as a scheduled task. Only create a clean build when absolutely necessary. A clean build occurs during the nightly build. If the build will not run unless a clean build has completed, check the dependencies to ensure that the build is running optimally.
- Consider the need to run iteration tests based on the time constraints for the build. Consult with the test manager as needed.
|
Exit Criteria
|
A build report is generated documenting the results of the build. | |
|
|
|
|
(C) 2005 Microsoft Corporation. All rights reserved.
MSF for CMMI Process Improvement: Build 050707 |
|