Activating Activities and Build 

Activities are stored in the DTR in two states:

·        Open: The versions of the activity exist only locally (or, after uploading, on the DTR server) and are visible only for the developer who created them.

·        Closed: The versions of the activity are stored on the DTR server and are visible for the developers of this software component.

To make the versions of an activity available for all the developers who use the software component, you must activate the activity.

To activate an activity, DTR and CBS cooperate. Activation is triggered by the developer. During the activation, the CBS tries to rebuild the components (DCs) changed by the activity. If this build is successful, it creates new archives for the DCs and finishes the activation by integrating the activities from workspace ‘inactive’ into workspace ‘active’. The changes become visible in both the active workspace and the archives created in the build. Typically several build requests are executed in parallel in CBS.

The figure shows the activation of activities. Two groups of developers share DTR and CBS.

The first group creates files for an application (1). The resources are stored in workspace inactive (2). The resources are built centrally in the CBS (3a-c). After a successful build, the CBS automatically sends an integration request for the activity to the DTR (4). The DTR integrates the activity into workspace active (5).

The second group uses the SC of the first group. When they need the resources of the first group, the CBS accesses either the workspace active or the archives of the SC stored in the CBS.

For more information on the build process, see Component Build Service – Build Concepts.