CBS Buildspace

The CBS supports the concept of the development configurations by so-called buildspaces. A buildspace is a separate area within a CBS, which implements exactly one development configuration. If you create a new track in the Change Management Service (CMS), the buildspaces for the development and the consolidation system are created automatically.

Like the development configuration, also a buildspace contains compartments for software component versions. There are two categories of software component versions:

·        Software component versions developed in this configuration

Changes to the respective development components are activated in this buildspace. The buildspace provides storage space for the build results.

·        Software component versions used in this configuration The relevant development components are built at a different place and imported into the buildspace.

Buildspaces always contain those versions of the involved software components that are suited for a configuration. This way, they provide the development teams with a consistent development context. A buildspace provides a semantically consistent environment, comparable to an R/3 development system, which facilitates the development work considerably.

The figure below shows the interaction between CBS buildspace, development configuration and DTR workspaces. In two buildspaces, two different states of the software component “WebShop” are built: 1.0DEV and 1.0CONS. In both cases, the software exists as source code, which is why both buildspaces for this software component refer to DTR workspaces. (For DEV and CONS, it is an inactive and an active DTR workspace each).

Interaction between CBS buildspace, development configuration and DTR workspaces.

In both buildspaces, the software components BusinessFramework and Technology are used. They are archives that were built in a different buildspace (usually on a different CBS) and imported into these buildspaces. In this example, in the DEV buildspace newer releases of the used software components were imported, while the CONS buildspace still uses an older version.

The consolidation with DEV and CONS states is not the only reason why you can have several buildspaces in one CBS. You can also use different buildspaces, for example, to build different releases of one software component or to develop completely different software components.