Contents
Module overview 4-2
Rational Team Concert build system architecture4-3
Developer build activities4-6
Monitoring team builds4-11
Compare builds4-21
Module summary 4-23
Exercise 44-24
Notes:
Instructor notes:
Purpose — List the unit objectives
Details —
Additional information —
Transition statement —
Instructor Notes:
Explain where you are in the course.
Build-engine objects:
Collect build requests, give requests to build computers that poll for requests, and manage results
Receive and store build requests from developers
Receive status reports from build engines during build execution
Store build execution results that the build engines return
Build computers:
Generate builds that Jazz™ Team Server dispatches
Poll Jazz Team Server for build requests
Run build scripts
Report build status and results to Jazz Team Server
Instructor Notes:
Explain where you are in the course.
Instructor Notes:
Explain where you are in the course.
Instructor Notes:
Explain where you are in the course.
Comparing builds is a useful diagnostic tool to pinpoint which change or changes caused the behavior of your application to change. Suppose you generated a build yesterday, and the application performed correctly. After the build today, however, the application stops responding when you try to use a specific function. You can compare the two builds to identify the work items that were included in current build that were not in yesterday’s build. From the change set information in each work item, you can identify the file-level differences between the two builds. In all likelihood, the cause of the problem in the build today was introduced in those file-level changes.
Notes:
Instructor notes:
Purpose — Summarize the unit
Details —
Additional information —
Transition statement —
Instructor Notes:
This lab takes approximately 15 minutes to complete.