From the Builds page, you can inspect past builds and monitor the progress of ongoing builds.
The Builds page provides the following information about current and past builds:
- Pipeline Name: The name of the pipeline that ran and the build number (Execution Id). Select the pipeline name to go to the Build details page.
- Status: The build status, such as running, failed, or success.
- Trigger: How the build started, whether by a webhook trigger or manually. Builds triggered by webhooks can include links to the associated PR or commit. For more information, go to SCM status checks.
- Executed By: The name of the user that started the build.
- Runtime: How long the build ran.
On the Build details page, you can investigate a variety of details about a specific build.
Pipeline tab (logs)
This tab shows the build stages and steps.
Select a step to investigate logs, inputs, outputs, and errors (if any) for that steps. If enabled, AIDA can provide troubleshooting assistance.
When troubleshooting failed builds, you can switch to Console View to allocate more screen space to logs. Once you've identified a potential cause, select Edit Pipeline to go directly to the Pipeline Studio.
Troubleshoot build log issues
Go to the CI Knowledge Base for issues and questions related to build logs, such as:
- Truncated execution logs
- Step logs disappear
- CI step logs don't load in real time.
- Step succeeds even when explicitly executing exit 1 in a Bash script that is runs in script's background
- A previous execution is missing from my Builds dashboard or Project Overview page.
This tab lists pipeline-level inputs. Step-level inputs are reported in the step details on the Pipeline tab.
This tab provides links to artifacts, such as images or reports, produced during the build.
Availability of artifact details depends on the upload location, build configuration, or build infrastructure. For an example and more information, go to Publish to the Artifacts tab.
This tab provides a list of commits that triggered the build, along with source code repo links, if applicable.
This tab presents test results from Run or Run Tests steps. For more information, go to View tests.
The Policy Evaluations, Security Tests, and Error Tracking tabs report Error Tracking information and information from other Harness modules and features, such as Harness Policy As Code, if these are enabled and included in the pipeline.
For information about Harness dashboards, go to the Platform documentation on Dashboards.
Error Tracking (Run Tests step)
If you enabled error tracking in the Run Tests step, a list of code error events are reported on the Error Tracking tab. For each event, the following are reported:
- Event Type and Description.
- Location in the code.
- Impact (Count) in terms of volume and spread across your application.
The following event types are reported:
- Caught Exception: Exceptions that were captured and resolved by the application.
- Uncaught Exception: Exceptions that were not captured by the application.
- Swallowed Exception: Exceptions that were captured but ignored by the application.
- Log Error: Events logged as errors in the application.
- Log Warnings: Events logged as warnings in the application.
- HTTP Errors: HTTP communication errors.
Select the event's Location to open the Automated Root Cause Analysis (ARC) page where you can view the source code, stack, variable state, and log statements leading to the error. This helps you analyze, troubleshoot, and remediate errors faster.