Build detail

The Build Detail shows information pertaining to a single continuous integration (CI) build including attributes like the build number, duration, build status, and associations to other activities like commits, reviews, and work items associated with the build. If the CI job is configured to run tests, this view also shows test summary information including the number of passed, failed or ignored tests.

Build Detail Attributes

The step associated with the current activity is highlighted. To see the detail for a different activity, click on the associated step.

The Build Detail displays these attributes:

Build Detail Attribute	Description	Location
Pipeline step number	The actual step in the pipeline that represents this activity.	Build activity header
Build number	The ID for a specific build supplied by the CI server.	Build activity header
Build source display name	The user defined "friendly" label for the build source job.	Build activity header
Timestamp	The date and time the build completed as reported by the CI server.	Build summary
Build duration	The time it took for the build to run, from start to finish.	Build summary
Build result	The final outcome of the build and corresponding external link to the build summary. The build result can be one of these states: `succeeded`, `failed`, `aborted`, `unstable`, or `unknown`.	Build summary
Test result	Test summary data is displayed in the following categories: `passed`, `failed`, or `ignored`. An external link to test results is also displayed. If + there are no associated test results, the following message is displayed instead: "`No test results`".	Build summary (icon and value)
Comment	Comment and user profile picture of the user who created the comment. A default user avatar is depicted if the user has not defined a profile picture in TeamForge.	Comment section

Build Associations

Builds may be associated with other pipeline activities such as commits as well as TeamForge work items. The Build Detail displays this information in the "Associations" section::

Commits — Commits are identified by the commit ID, and may be linked to the corresponding commit details page. TeamForge Orchestrate makes no assumptions when associating commits to builds; the list of associated commits originates from the build source. Commits are linked to the related commit detail only if TeamForge Orchestrate is monitoring the SCM repository in question; else, only the commit ID is displayed.
Missing commit details — TeamForge Orchestrate sometimes learns about commits before the details of these commits are officially reported by the SCM source. Such commits are grayed out temporarily in the "Associations" sections of Review and Build Detail pages until TeamForge Orchestrate receives this information and can create a Commit Details page. Traceability graphs include these commits, but you cannot click on the commit nodes to get commit details. See Troubleshooting TeamForge Orchestrate for information on commits with missing detail information.

See Commit detail for information about commit details.
Reviews — Reviews are associated with builds through the commit + associations that they both share in common. Review requests are identified by the source display name (user inputted) and review ID. Reviews are linked to the corresponding Review Detail page.
Work Items — Work items are associated with builds through the commit associations that they both share in common. See Associate code commits with other items