Using the CBS Buildspace Details View

Use

The CBS Buildspace Details view contains detailed information on DCs, sorted by buildspace and compartment. In addition, you can start the build of an entire compartment in this view.

Procedure

Start the CBS Web UI.
To reach the CBS Details view, choose one of the options below:
- In the Buildspaces View, select a buildspace by clicking its name and then select a compartment.
- In the Compartments View , select a buildspace from the dropdown list The selected Buildspace is and then select a compartment.
  
  Note
  If you do not select a compartment, the worst case of all build variants is displayed.
  
  In one variant, a DC can have status broken, in another it can be correct. This is considered in the display of Usages.
Select one of the following processing tab pages:
- Development Components : Details for DCs of the compartment.
- Workspaces : Available workspace paths - these are available only for compartments that contain sources.
- Build the Compartment : This option is offered only for compartments that contain sources.

Development Components

Details for DCs depending on their properties and statuses

Under Select , select one of the follwowing options to receive the required information:
- AllDCs . All DCs in the selected compartment.
- Broken by itself DCs : DCs with defective metadata or build errors.
- Broken due to Used DCs : DCs with cyclic dependencies or DCs that use DCs with status broken .
- All OK DCs : Lists development components that have been built successfully and are not scheduled for rebuild.
- Broken DCs : All DCs that cannot be built successfully. Lists the development components that:
  - Had been "dirty" and then the necessary rebuild failed.
  - Were activated by force even though the build failed.
- Dirty DCs : Lists development components that are scheduled for rebuild:
  - Because some used component was changed or
  - Because the administrator requested rebuilding the whole compartment.
    
    If the rebuild is successful, the component will go into state "OK". If it fails it will be "broken".
- DCs with Collisions .
Under Build Variants , select the relevant variant: The results can differ for different build variants.

You can select among the following details:
- DC Name : The name of the development component.
- DC Vendor : Name of the organization, which originally defined this development component.
- Collisions : For all compartments containing source files a link to the DTR is displayed. Here, you can view the collisions of the selected DCs and their child DCs.
- Compile State : Displays the status of the DC builds using a traffic light:
  - Green : The DC has been built successfully.
  - Red : The DC has not been built successfully due to a build problem.
  - Yellow : The DC is currently being built or is scheduled to be built.
  - No color: The build status cannot be determined, because DC metadata is defective or the DC has cyclic dependencies or uses DCs in status broken .
- Metadata : Shows a red light if there is a problem with the component definition. Examples: component has references to non-existing components; component definition file (.dcdef) cannot be read, etc.
- Cyclefree : Shows whether cyclic dependencies exist - they terminate the build process. Shows a red light if a cyclic dependency exists.
- Usages : Shows whether DCs in status broken are used. Shows a red light if such DCs are used. This information also depends on the selected build variant. You can display the used DC by clicking on this build.
- Pending Activites : For all compartments containing source files, there is a link to the pending activities of the selected DC and a link to the DTR, where you can view the details for the activity.
- Unreleased Activities : For all compartments containing source files, there is a link to the DTR, where you can view the not yet released activities of the selected DC.
- All Activities.

When you select the name of a DC, the CBS Web UI: Development Components View is called.

Workspace Details Tab Strip

Displays the URL of the active and inactive DTR workspace for this compartment. If the compartment contains only archives no DTR workspaces are assigned.

Build the Compartment Tab Strip

Administrators are allowed to request a build for all development components in the compartment. The "Build the Compartment" tab strip is only displayed if activation is allowed for the compartment.

In the development component tab strips you can navigate to the Development Components Details view by clicking the name of the development component.

Initialize Compartment Button

The CBS will purge all information about the content of the compartment. This includes data about development components, build results, and DTR activities. After this cleanup is done, the CBS reads all component and activity related data again from the active DTR workspace. Finally a build is scheduled for all development components in the compartment.

When a buildspace is created, the CBS automatically creates "initialize compartment" requests to read any data that may already exist in the affected DTR workspaces.

The build results and the component data, which are stored in a compartment of a CBS buildspace, should always reflect the content of the associated active DTR workspace. This is guaranteed by the activation mechanism. However, there could be situations where CBS compartment and active workspace are no longer consistent. This could happen if you have to restore the database of CBS or DTR from a backup. In these cases you must initialize the CBS compartment from DTR again.

The "Initialize Compartment" button is only displayed if activation is allowed for the compartment.

Note

When you click "build compartment" or "initialize compartment", the operation is not executed immediately. Instead the CBS creates a request and puts it into its request queue. The request is then executed later by the CBS service. The Web UI displays the request ID of the request that was created. By clicking on the request ID you can navigate to the Requests view and view more details.