Activation in the CBS

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

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

If during the build an error occurs (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 do not change. Only if the activation is successful are the build results copied to the archive pool and the DTR activities are integrated into the active workspace.

Activation Sequence

It is important to activate the activities of the Design Time Repository in the correct sequence. The CBS guarantees this with the check for overlappings. 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 are overlappings with younger or not yet activated activities, you can integrate them 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 on component level if both activities contain files that belong to the same development component.