Activation in the CBS 

The smallest units that can be built in the Component Build Service (CBS) are development components (DCs). When a change is activated, the CBS determines the involved DCs and rebuilds them in the scope of the activation request.

Of the used DCs, always the latest build results from the archive pool are used. Of the DCs to be built, the changed files to be activated are taken from the inactive workspace, while for all other files of the DCs the active version is used.

If an error occurs during the build (for example, because of a syntax error in a Java file to be compiled), then the entire activation is rejected and the state of the archive pool and of the active workspace does not change. If the activation is successful, the build results are copied to the archive pool, and the DTR activities are integrated into the active workspace. In this case, the build is successful and the activation is accepted.

For more information about the DCs, see Development Components.

Activation Sequence

It is important to activate the activities of the Design Time Repository (DTR) in the correct sequence. The CBS guarantees this with the check for overlapping. Every DTR activity contains versions of files in the DTR. Two activities overlap on data level if there is at least one file that was changed in both activities.

In this case, the activity that was the first to be checked in or integrated into the inactive workspace must also be the first to be activated. If there is an overlap with younger or not yet activated activity, you can integrate it into the activation or cancel the activation.

Optionally, you can request a more severe overlapping check on the component level when you start the activation request. Two activities overlap at component level if both activities contain files that belong to the same development component.

For more information about activities, see Activity.

Activation in Case of Errors

Usually, changes that contain errors are not activated, because the build fails. In special cases, it may be necessary to activate changes with errors. To do this, use a special option at activation (activate even if build fails). If a change is activated even though the build fails, all involved development components are in an inconsistent state: the DTR activities were integrated into the active workspace, but no corresponding build results could be written to the archive pool. CBS flags the inconsistent development components as BROKEN.