Ctrlk
Contact SupportProduct
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Build Monitor

Inspect build scans, test-stage executions, and agent command details.

Use Build Monitor to inspect a reported build and its test stages.

Open a build

Select an app, branch, and build to open its overview.

Build Monitor build overview showing app, branch, and build selectors.
Build Monitor opens after you select an app, branch, and build.

Review build session and scan details

The build overview shows the first two commands required to report a build to SeaLights:

  • config — generates the Build Session ID (BSID).

  • Build scan — analyzes the application bytecode.

Review test-stage details

View Test Stage-specific data by selecting a Test Stage on the right-hand side of the screen.

Build Monitor showing a selected test stage.
Select a test stage to view its execution data.

Review executions

This tab lists every execution associated with the selected test stage. These executions contribute to the duration, coverage, and test counters.

When you run the same tests against the same build, the test counters and duration will be aggregated. For example, two executions of 10 tests each show 20 reported tests and two executions.

Each execution shows its status, start and end times, Lab ID, and ending cause.

Executions tab with execution status, timestamps, Lab ID, and ending cause.
The Executions tab lists the activity that contributes to test-stage metrics.

A test-stage execution has three statuses:

Created The execution is in progress.

Pending Delete SeaLights received the end event and is processing it. This state lasts no longer than 120 seconds.

Ended Processing is complete. Metrics are available in the SeaLights dashboard and reports.

View ending-cause definitions

The Ending cause column can contain these values:

Ended by an agent or API

  • Agent — an agent command ended the execution.

  • API — an API request ended the execution.

Ended automatically

  • Server - Conflict — SeaLights detected conflicting execution parameters and closed the older execution. For example, the same Lab ID was used for another test stage.

  • Server - Timeout — an API-configured timeout ended the execution. The default timeout is four hours.

  • Server - Daily — SeaLights closes executions that remain open for over 24 hours. This happens daily at 3:00 AM GMT.

Ended by Support

  • SeaLights Support — Support manually ended the execution for troubleshooting or ticket resolution.

Troubleshoot advanced cases

Review agent command JSON

In the Build Scanner and Test Listener tabs, view JSON session parameters mapped from agent commands.

Build Monitor panel showing JSON command details.
Inspect the JSON parameters submitted by the agent command.
Build Monitor showing agent command JSON details.
Use command details to compare the reported session parameters.

Validate pull request integration

Pull request jobs do not appear on the dashboard. Review them in Build Monitor instead.

  1. Select the pull request branch. Pull request branches are hidden by default.

  2. Select the expected build.

  3. Confirm the build session and pull request data.

If the branch or build is missing, review the Pull Request integration setup.

Build Monitor displaying a pull request branch.
Enable pull request branches to find pull request build data.
PreviousSeaLights Cockpit
NextLive Agents Monitor

Last updated

Was this helpful?