Build Configuration

Select the build configuration that you want to build.

• Displays build configurations:

  • Those associated with the current Dimensions CM project.

  • Those where the selected items have affected targets.

• Displays the latest checked-in versions of the build configurations in the following format:

  <build configuration name>;<version>

  For example: build_test;2

Baselines only:

• You can build only configurations associated with the Dimensions CM project from which the baseline was created.

• Build configuration versions with the prefix ’*’ were checked in when the baseline was created against the Dimensions project. These are the latest versions of the build configurations at the time the baseline was created.

• Build configuration versions without the prefix ’*’ were created after the baseline was captured for the project.

Build Stage

Select the deployment stage at which the targets will be built. To build in a work area select <none>.

Not available for baselines.

Build Area

Select the build or work area where the targets will be built.

Baselines only: select a work area where you want to build the baseline.

(Not applicable to baselines) To build all deployment areas associated with the stage select <All areas>.

Baselines only:

• Work areas above the divider are areas set up for the build configuration that you have selected and you have access to.

• Work areas below the divider are all other areas to which you have access.

Build Area User

Enter the ID of the Dimensions user who owns the area. You also need to enter and confirm their password.

Only displayed if required.

Start search path from stage

Select the stage where you want the search path to start.

Only available if you selected a work area.

Download files to work area

Select an option for downloading files to your work area before the build is executed.

• Only available if you selected a work area.

• Not available for baselines.

Apply system date/time to downloaded files

Select this option to apply system date/time to files that are downloaded.

Check in build outputs automatically

(Optional) Captures the outputs of the build and checks them into Dimensions automatically.

Specify the request(s) the build outputs will be related to

Click Select and use the Request wizard to select one or more requests that the build outputs will be related to when they are checked into Dimensions.

You can also enter the request IDs in the following format:

"QLARIUS_CR_44", "QLARIUS_CR_43"

Required if your process model specifies that checked in items have to be related to a request.

Specify the project where the build outputs will be checked in to

To check the build outputs into a different project or stream click Select and use the Select Project/Stream wizard to select a different project or stream

Build Options

Select build options and add options in the Other Build Options field.

• 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. Only applies 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: only builds targets whose source is at the correct stage.

For details of the build options, see the templating language and processor section in API reference.

Target Selections

Choose target selections for the target list.

If you change target selections, click Re-query to repopulate 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.

Build Targets List

Select one or more targets 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 file name 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).

• Details: 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.

• Displays targets that are:

• Impacted by the items that you selected.

• Associated with the build configuration you selected.

• 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 Dimensions Build.

• 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 ran with output collection enabled, the 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. For example, 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 only select target A then target B will automatically be built as it is impacted by the same source file.

Summary

A summary of the build activity and command.

Display only.