Build Dimensions CM requests

This topic describes how to build a Dimensions CM request.

When you build a request all the targets affected by items that are related In Response to the request are built. You can only build a request if the Dimensions CM project/stream to which it belongs has one or more build configurations. For details about creating build configurations, see the Dimensions Build help.

If you are building to deployment areas, first assign them to the Dimensions CM project/stream associated with the build configuration. For details, see Assign deployment areas.

About build configurations

The Build Configurations list in the Build wizard displays only the following build configurations:

  • Those associated with the current Dimensions CM project/stream.

  • Those where the items in the requests have affected targets.

    For example:

In the example above, the Build Configuration list displays Build_configuration_1 because Item_1 in Request_1 has an affected target. Build_configuration_2 is not displayed because Item_2 in Request_2 does not have an affected target.

The Build Configuration list displays the latest checked-in versions of the build configurations in the following format:

<build configuration name>;<version>

For example, if you have two versions of the build configuration ANT_JAVA that are checked in, ANT_JAVA;2 and ANT_JAVA;2, the list displays the following:


PRIVILEGES: Build from a project/stream.

To build a request:

  1. In the web client, open the project containing the request that you want to build.

  2. In the content pane of the Requests tab, select the request you want to build.

    Or in the History tab of the Deployment view, select the request you want to build.

  3. In the menu area, click Build and choose Build.

    The Run Build wizard opens, displaying the name of the current Dimensions CM project or stream.

  4. From the Build Configuration list, select the build configuration that you want to build.

  5. From the Build Stage list, select the deployment stage at which the targets will be built. To build in a work area, select <none>.

  6. From the Build Area list, select the build or work area where the targets will be built. To build all deployment areas associated with the stage, select <All areas>.

  7. If required, in the Build Area User field enter the ID of the Dimensions CM user who owns the build area. You also need to enter and confirm their password.

  8. If you are building in a work area:

    • From the Start Search Path From Stage list, select the stage where you want the search path to start.

    • From the Download Files to Work Area list, select an option. The files are downloaded before the build is executed.

    If you select All or Selected Only, you can also select the option Apply system date/time to downloaded files.

    Click Next.

  9. To capture the build outputs and check them in to Dimensions CM, select the option Check in build outputs automatically.

  10. If you are checking in build outputs:

    • To specify the requests that the build outputs will be related to when they are checked in to Dimensions, in the Specify the request(s) field click Select. In the Request wizard, select one or more requests. You can also enter the request IDs in the following format:

      "QLARIUS_CR_44", "QLARIUS_CR_43"

    • To check the build outputs in to a different project or stream, in the Specify the project where the build outputs will be checked in to field click Select. In the Select Project/Stream wizard, select a different project or stream.

      Click Next.

  11. Select build options:

    Audit area(s) before build Produces an audit report for the build areas associated with the Dimensions project/stream. The report is produced before the build.
    Clean area(s) before build Runs the clean script (in the build configuration).
    Lock area(s) in search path Locks all deployment areas associated with the build and prevents other changes to these areas while the build is running. Applies only to work area builds.
    Rebuild all targets

    Rebuilds all targets. If you select this option, the following option is also available:

    Targets only in the current stage: builds only those targets whose source is at the correct stage.

  12. Enter additional options in the Other Build Options field. Click Next.

  13. Choose target selections for the target list:

    Show all targets from build configuration Displays all targets from the build configuration.
    Show final targets only Does not display intermediate targets.
    Show foreign items Displays items that are related to items in a different project or stream.
    Show side-effect targets Displays files created at the same time as the main target, such as a compile listing.
    Show predicted targets Display targets based on a previous revision of the item. This is relevant when the selected revision has not yet been built.
    Include targets impacted by related requests Considers child requests as well as the parent request.
  14. If you change target selections, click Re-query to repopulate the target list.

  15. From the Build Targets list, select one or more targets to build. The list displays all targets that are impacted by the objects that you selected to build.

    For each target in the list the following build dependency information is displayed:

    Target The name of the target as defined in Dimensions Build.
    Filename The filename of the target or mask as defined in Dimensions Build.
    Found In

    The relationship of the objects that you are going to build to the target. Can be one of the following:

    • Build Config: matches a rule in a build configuration (explicit relationship).

    • BOM: named in a bill of materials (BOM) from a previous build (implicit relationship).

    • Build Config/BOM: matches both of the above (explicit and implicit).

    • <blank>: no matches were found for the selected objects.

    Build Config The build configuration that you selected. The configuration version may be different from that in the Build configuration list (the latter is ignored when this data is processed).

    Can be one of the following:

    • Prediction. The relationship is based on a previous revision of the item.

    • Foreign. Is related to an item in a different project or stream.

  1. Click Next. A summary of the build command is displayed.

  2. Click Finish and monitor the progress of the build.

Guidelines and behaviors:

    • You must select a target to perform a build.

    • By default, targets are automatically selected so you only need to use this list to filter the list of targets being built. You can disable the automatic selection of targets. For details, see Disabling the Automatic Selection of Targets.

    • When dependency information is available from previous builds, it is used to approximate impacted targets. However, this approximation is based on stored data and the actual build result may be different.

    • If a specific target cannot be matched against the objects that you selected, all targets for the selected configuration are displayed.

    • If previous builds were executed with output collection enabled, the Build Targets list also displays item relationships that were discovered during the build (as long as the build tool can provide this information). This enables you to view and select targets by name instead of only by build configuration build rules.

    • When you specify a target to be built, additional rules may apply that result in additional targets being built.

      Example: Suppose you specify that all impacted targets for a source will be built. Source file X is used to build targets A and B. If you select only target A, then target B will automatically be built, as it is impacted by the same source file.

Back to top

See also: