A buildspace provides the information which source files and archives are taken for build requests (and from where they are taken).
Creating Buildspaces
A buildspace is created in CBS by importing a development configuration file. It contains all archives needed for the software component development and stores all build results. One CBS can host multiple buildspaces. Each buildspace is self-contained in the sense that a buildspace is independent from other buildspaces. Each buildspace can be configured in a different way having a separate and isolated build environment. In an abstract manner a buildspace represents a "logical build server" inside CBS.
A CBS that has been deployed on a freshly installed AS Java does not contain buildspaces. To check which buildspaces are available on a CBS use the CBS Web UI. A CBS without buildspaces cannot process any build requests.
Editing Buildspace Settings
You need administrators' rights to edit buildspace settings.
Start the CBS Web UI and open the Buildspaces View .
In your browser, go to the CBS Web address: http://<host>:<port_number>/tc.CBS.Appl . Open the CBS Web UI link.
Select a buildspace to edit and choose Edit .
The editor area opens.
Make settings for:
Input Mode
Request Processing Mode
Output Queue Mode
Output Pool Mode
Log Expiry
The setting Active cannot be changed here.
Save your settings.
Deleting Buildspaces
Normally CBS Administrators should not delete buildspaces in CBS Web UI. Deleting a single buildspace may put the development landscape into an inconsistent state. Instead the delete track function of the Change Management Service (CMS) should always be used. Deleting a CMS track automatically deletes the associated buildspaces.
If the track deletion in CMS should fail for some reason, CBS administrators can delete a buildspace manually.
Start the CBS Web UI and open the Buildspaces view
In your browser, go to the CBS Web UI: http://<host>:<port_number>/tc.CBS.Appl . Open the CBS Web UI link.
Select a buildspace to delete and choose Delete .