Dependency build reports
Build reports provide information about the source of the build, language definition, and the build map.
- 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.
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.
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.
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.