Build items

This topic describes how to build one or more items.

The items that you build are sources related to targets in a build configuration; the targets affected by the source items are the output of the build. You can also specify a wildcard as a source for a target. For example, if you specify *.java as the source for the target WebApp.jar, when you build any Java file, the target WebApp.jar is built.

You can only build items if the Dimensions CM project/stream to which they belong 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.

You cannot build multiple item revisions that are at different stages.

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 that you selected have affected targets.

    For example:

In the example above, Build_configuration_1 contains Item_1 that affects Target_1 and is displayed in the Build Configuration list. However, Build_configuration_2 is not displayed as the item it contains does not affect any targets.

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;1 and ANT_JAVA;2, the list displays:

ANT_JAVA;2

PRIVILEGES: Build from a project/stream.

To build items:

  1. In the desktop client, open the project or stream containing the items that you want to build.

  2. In the My Current Project/Stream window, expand the Catalog node and select Items. In the Items object window select the items that you want to build.

    Note: You can also use other methods to display items that you want to select. For example, you can use the Find Item dialog box, run an item report, or open the Folders and Items view.

  3. From the Item menu select Build Items. The 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>.

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

  7. 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.

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

    • 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, 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.

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

    Click Next.

  9. Select the following 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.

  10. In the Other Build Options field, enter additional options, and click Next.

  11. Select the dependencies and targets to be built:

    Deployment Analysis Runs dependency analysis.
    Predicted (using soft relationships) Displays targets based on a previous revision of an item. This is relevant when the selected revision has not yet been built.
    Foreign (cross project dependencies) Displays items that are related to items in a different project or stream.
    Side effect (from observed builds) Displays built items created at the same time as the main target, such as a compile listings and secondary targets.
    Configuration analysis Analyzes the build configuration.
    Final targets only Does not display intermediate targets.
    All targets Displays but does not necessarily select all targets in the build configuration.
    Targets impacted by related requests Considers child requests as well as the parent request.

    For more information, see the BLD command in the Command-line reference.

  12. If you change targets, click Query to repopulate the build target list below.

  13. 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).
    Details

    Can be one of the following:

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

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

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

  15. 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 ran 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 are to be built. Source file X is used to build targets A and B. If you select only target A, then target B is built automatically, as it is impacted by the same source file.

Back to top

See also: