Workflow for building components


The build components task of the integrator follows create a testing stream and precedes make baselines.

Before you make new baselines, build the components in the integration stream by using the current baselines plus any work that developers have delivered to the stream since you created the current baselines. Lock the integration stream before you build the components to ensure that you work with a static set of files.

If the building and testing succeeds, you can make baselines that select the latest delivered work. If your project uses feature-specific development streams, perform this task on those streams and on the integration stream.

HCL VersionVault MultiSite consideration

Typically, developers complete the deliver operations that they start. If your project uses HCL VersionVault MultiSite, you may need to complete some deliver operations before you can build the components. Many HCL VersionVault customers use HCL VersionVault MultiSite, a product layered on HCL VersionVault, to support parallel software development across geographically distributed project teams. Using HCL VersionVault MultiSite, developers can work on the same VOB concurrently at different locations. Each location works on its own copy of the VOB, known as a replica.

To avoid conflicts, an exclusive-right-to-modify scheme, called mastership, is used. VOB objects, such as streams and branches, are assigned a master replica. The master replica has the exclusive right to modify or delete these objects.

In a HCL VersionVault MultiSite configuration, a team of developers may work at a remote site, and the integration stream of the project may be mastered at a different replica than the developers' development streams. In this situation, the developers cannot complete deliver operations to the integration stream. As integrator, you must complete these deliver operations. UCM provides a variation of the deliver operation called a remote deliver operation. When UCM determines that the integration stream is mastered at a remote site, it makes the operation a remote deliver operation, which starts the deliver operation, puts it in a posted stated, but does not merge any versions. You then complete the posted deliver operation at the remote site.