IBM SC34-4499-03 manual Verifying and testing part updates

Thus, work area 310 contains the following parts:

brain.c	leg.c
brain.obj	leg.obj
brain.exe	foot.c
arm.c	foot.obj
arm.obj	optics.c (modification 1)
hand.c	optics.obj
hand.obj

Work area 310 continues to contain the unchanged parts from the requested release view, but now the work area is overlaid with changes local to the work area Ð optics.c in this case. Alex has his own copy of the application that he can modify without impacting other developers. Alex has checked in optics.c; however, the modi®ed part remains locked until the work area is integrated with the release.

Verifying and testing part updates

Alex now requests a build of brain.exe, the high-level program for the robot control application.

GUI

From the GUI, he:

1.Selects Parts → Build from the Actions pull-down menu. The Build Parts window appears.

2.Types the following, and then selects OK to start the build:

vbrain.exe in the Path name ®eld

vrobot_control in the Release ®eld

v310 in the Work area ®eld

vnormal in the Pool ®eld

The Pool ®eld tells TeamConnection which set of build agents will handle this build. Alex got the name of the pool from his build administrator.

Alex could have selected brain.exe from a list of parts on the Parts window, and then selected Build from the Selected pull-down menu. This action would have placed some information in the ®elds, such as the path name and release name.

60User's Guide