Dependency build reports

Build reports provide information about the source of the build, language definition, and the build map.

To view the build report, open of the following tabs in the build result:

Overview tab: Click the link for the Build Report under the Contribution Summary section.
External Links tab: Click the link to buildReport.xml.
Build Report tab: Displays the build report.

The build report is displayed in an embedded editor on the BuildReport tab. The BuildReport tab contains tabs that display the status of the buildable files: Successful, Failed, and Not Built. The Failed and Not Built tabs are only included if the build fails. The editor displays the resource prefix for the source files. The component label is included in parentheses with the project name.

In the editor, you can browse the build result details. You can use the pagination, sort, and search functions to easily find and view the build entry that you are interested in. You can change which source files are shown in the build report using the Filter field, which supports the wildcards asterisk (*) and question mark (?). In addition, related build artifacts are connected with the build entry. You can double-click the links under the columns to view dependency sets, language definitions, and build maps.

The content in the build report page is based on projects. The build report shows as many projects and source files as possible. However, you can change the number of rows to display in the build report in the preferences for the Dependency Build. If the number of build files are lower than or equal to the number that is defined in the preference, only one page is shown. For example, if you set the number of rows to display on the build report page to five, the number of entries shown in the example exceeds the maximum size of the build report page. Since only five entries can be shown on the page, the results of the different projects are displayed on individual pages.

An example of the build report editor limited to five lines

In the build report editor, place your cursor over a link to a source file to display the buildable file path, the project name, and the component name. Place your cursor over a value under the Reason to Build column to display the definition of the value. Place your cursor over a value under the Language Definition column to display the description of the language definition. For a possible explanation of negative return codes coming from TSO or ISPF translators, place your cursor over a value under the Max Return Code column to display the description of the return code.

Double-click a link in the Source column to display the dependencies of the file in a Dependency Set view. You can also open the Dependency Set view for preview builds and personal builds.

In the Dependency Set view, the File Changed column indicates whether the file changed in the dependency build. The Version ID column indicates the version of the file in the source control management system.

An example of a Dependency Set view displayed by clicking a source file link in the build report editor

The build report provides links to the corresponding build maps and any other details about the build. Double-click the icon for the source file in the Build Map column to open the build map in an editor.