Show TOC

Buildspaces ViewLocate this document in the navigation structure

Use

In this view you can view the currently existing buildspaces and their settings.

If you choose a buildspace name, the Compartment view automatically opens and shows the compartments within the buildspace.

You use the Buildspace view to edit buildspace settings or to delete buildspaces.

Editing Buildspace Settings

You can view or edit the following buildspace settings for each buildspace.

Active

While a buildspace is being created or initialized, the buildspace is switched into inactive mode. This may take some time. During this time, no operation can be performed on the buildspace. After the initialization the status is automatically switched to active again.

Input Mode

This parameter controls how incoming build requests are handled for this buildspace:

  • OPEN: Component Build Service (CBS) accepts build requests for the buildspace

  • PRIVILEGED: CBS accepts build requests for the buildspace only if privileged users send them.

  • CLOSED: CBS accepts no new build requests at all.

    Note

    Switching to a more restrictive input mode only affects new build requests. Requests that already exist in the queue are still processed.

Request Processing Mode

This option allows switching of the CBS build engine. If OFF, build requests are no longer processed but remain in the build request queue. If the input mode is OPEN or PRIVILEGED, users may create new build requests even if the processing is switched OFF. But these build requests remain in the queue until processing is switched on again.

Queued Requests

Specifies the number of build requests currently pending in the queue of this buildspace.

Processing Requests

Specifies the number of requests currently processed in this buildspace.

Failed Requests (Last 7 days)

Specifies the number of build requests failed in the last seven days in this buildspace.

Total DCs

Specifies the total number of development components in this buildspace.

Broken DCs

Specifies the total number of broken development components in this buildspace.

Output Queue Mode

This parameter can have the values QUEUED and NOT QUEUED. This setting affects how CBS handles old build results after a DC was successfully rebuilt. If the parameter is set to NOT QUEUED, the old build results are overwritten. If the value is QUEUED, old build results are kept in a queue until they are explicitly confirmed. One application for this feature is the automatic deployment of build results into a central test system. The service that does the automatic deployment confirms the build results after they are successfully deployed.

Output Pool Mode

This option implements an emergency stop so that build results cannot be retrieved from the CBS either for automatic deployment or for download by development tools. Normally this option must be set to ON. In case of a technical emergency, you may set it to OFF.

Example

This may happen if you know that the build results are somehow corrupted and you do not want to distribute them across the whole development landscape.

Log Expiry (in Days)

For each build request, the CBS creates a log and stores it in its database. In order to save space in your database, you should not keep these logs forever. Use this option to set the number of days after which the logs are automatically deleted by the CBS.