Dependency build maps

Build maps provide information about build inputs and outputs.

When you run a dependency build, a build map is created for each source file. During the build process, build maps and files are compared to determine whether inputs and outputs are synchronized or if something changed since the last update. If something changed, a rebuild is required.

Build maps are stored on Jazz Team Server, not in the file system of the build systems.

During builds, a time stamp is based on one of these conditions:
  • For source files in source control, time stamps are based on time stamps.
  • For z/OS® outputs, which are not program objects, time stamps are based on modified time in ISPF statistics. For more information about ISPF statistics, see Using ISPF Statistics in Ant-based z/OS builds.
  • For z/OS program objects, time stamps are based on values that are stored in SSI.
  • For IBM® i outputs, time stamps are based on time stamps that are stored in the file system.

During promotions, time stamps in build maps are verified and the build maps are also promoted.

You can open the build map from the dependency build results. Use the build map to view build dates and times, all of the components in a build, such as copybooks and source modules, and how those components are related.

To open a build map, double-click the icon for the source file in the Build Map column of the build report. For the build maps to be linked in the build report, the Publish build map links option must be selected on the build definition. By default, the option is not selected.
Note: A personal build does not generate a build map.
The build map opens in the build map editor displaying the Overview tab, with other tabs for the inputs, outputs, and details for the build map. Links to the related artifacts enable you to view the repository workspace, language definition, build definition, build result, and snapshot.
The contents of the build map Overview tab

The Inputs tab displays each input file that is in the build map, the path to the build source file, the type of the output file, and the version ID of the source file, which indicates the version of the file in the source control management system. Parenthetical information under the Dependency Resource column of the Additional Files from the build machine section of the build map indicates the origin of the file.

The contents of the build map Inputs tab
Beside the Files from the build machine produced by other builds in the build map, you can click Retrieve File Details to get more information about the files. The Progress tab of the client displays the retrieved information. When you right-click a resource in the Source Location column to open a context menu, you can select to open either the local or remote version of the file.

The Outputs tab displays the output file location and the associated resource definition.

The contents of the build map Outputs tab
Click the link for a resource definition to open the resource definition in an editor.

When publishing is enabled for a DD, the PDS information is stored in the build map. A link to the PDS can be found on the Logs tab of the build map editor. When IBM Developer for z Systems® is integrated with Rational Team Concert™, the value in the File Location column is a link that opens the remote member.

The contents of the build map Logs tab

The Details tab displays a textual overview of the build map information.

The contents of the build map Details tab


video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki