How to Review Build and Task History

Retrieve the details and outputs of builds and tasks run on the Signaloid Cloud Compute Engine.

Feature Highlight

The Builds and Tasks page is where you inspect, manage, and re-run work on the Signaloid Cloud Compute Engine. It covers everything started from the Code Playground, from a connected GitHub repository, and from the Compute Engine API, including the Signaloid CLI.

The platform stores every build and every task you run, so you can come back later, read the output, and start a new task from a build that already compiled cleanly.

This guide covers how to:

• See the builds and tasks you have run on the Signaloid Cloud Compute Engine.
• Open the outputs of any past task.
• Start a new task from an existing build without recompiling.

A Build is one compilation of your source code. A Task is one execution of the resulting binary. A successful Build is reusable, so you can launch new Tasks from it without compiling again. See Builds and Tasks for every field a card carries and the full status list.

The Builds and Tasks page

Open the page from the sidebar Builds and Tasks item. The sidebar item carries a small badge with the combined count of currently active tasks and active builds, so you can spot work in flight without opening the page.

The page has two top-level tabs: Tasks and Builds. Each one splits into an active and a completed section, so the Tasks tab holds Active Tasks and Completed Tasks, and the Builds tab holds Active Builds and Completed Builds.

Figure 1. The Builds and Tasks page lists everything you have run on the Signaloid Cloud Compute Engine, separated into active and completed sections. Hover over the duration icon on the Tasks tab to view information about the task timings.

Tasks tab

The Tasks tab lists every execution on your account. Locate the run you want by its source and status, then open its details to read the output. For every field and control a task card carries, see the Builds and Tasks reference.

Builds tab

A successful build is reusable. You can start a new task from it without recompiling. On a Completed build card, click Run Task to launch a new task with the build's stored arguments and data sources. Use the Command-Line Arguments () and Mount Data Source () buttons on the card to override those defaults first. The new task appears in the Tasks tab, and View Outputs on the build card opens its stdout and stderr once it finishes. Figure 2 shows overriding the arguments and the mounted data source before running. For every field a build card carries, see the Builds and Tasks reference.

Figure 2. Overriding the command-line arguments and the mounted data source on a successful build card, then clicking Run Task to launch a new task with the updated configuration.

The Task detail page

To open the Task Detail page, either click Show Details on a task card or click the task ID in the Build and Task control bar (Figure 3). The page displays the task's output, runtime statistics, and C0 execution time. Hovering over the Core () badge shows the details of the Core used for the task.

Figure 3. The Task Detail page shows the output of the task alongside runtime statistics such as C0 execution time. Hovering the Core badge reveals details of the core used for the task.