The build process consists of the following operations. Build managers perform the operations many times during a product release. Each of the operations contains several steps. As you work through the steps for each operation, the build management process takes shape.
Synchronizing the work areas ensures that the work areas are updated with changes from the database, for example, even if changes were performed through DCM operations.
Information about sync is in Synchronizing a work area with changes from the database.
When you update a project hierarchy, you update the members of the hierarchy with the object versions associated with the tasks in the build management folders.
Information about update is in Update guidelines.
A conflict is a potential problem with a project. Keep in mind, however, that not every conflict indicates a problem. When you resolve a conflict, you correct the problem with your project configuration.
You are not required to check out the products of a build before performing the build, but some preparation of the products is necessary.
If you use UNIX link-based work areas for this build, you must do one of the following steps. Check out all controlled products that might be updated by this build. Delete the links from the product files in the work area to the database. Convert these links to copies. If you do not perform at least one of these steps, you might overwrite versions of the products for the wrong release or purpose.
If you use copy-based work areas on UNIX or Windows, check that you followed step 10 ("Ensure copy-based product files are modifiable") in Creating the integration testing projects. If you did not follow step 10, you must check out the products to be updated during this build.
Information about the build is in Following build guidelines.
This second synchronization ensures that new or updated products are copied from the work area to the database. Additionally, the new or updated versions of products are automatically checked out, if necessary.
Specify a list of files to sync by using the ccm reconcile command. The build usually creates new or modified product files, so you can use the product file names as arguments to the ccm reconcile command. Specifying product file names is more efficient because you do not reconcile the entire work area.
The command is ccm reconcile -udb product1 product2... To learn more about this command, see Synchronizing the database with changes from a work area.
The first
time you perform a build, control the new products to be added under Rational® Synergy control.
Use the Sync Work Area dialog box. Right-click
over the project and choose Sync Work Area to
synchronize the database with the new work area files. The Work
Area Conflicts dialog box displays the conflicts. Filter
the conflicts by clicking and choosing Conflict.
In the list box next to the Filter icon, choose File added
to the work area. Select all the new products to be added
to the work area and click
. (See Syncing work area with database for details.)
After creating products, or after the first build in a new platform or release, ensure that all controlled products are marked as products. Mark products so that they are associated with the correct tasks.
Start the Properties dialog box by right-clicking over each product and choosing Properties. Ensure that the Is Product checkbox is set.
From the CLI, type this command:
ccm attr -c is_product -f -t boolean -v TRUE product1 product2 ... To learn more about attributes, see Creating an attribute
Information about providing applications is in Providing the application for testing.
Ensure that you have done the following tasks: