Repository Runs
Run on a connected repository card sends the repository to the Signaloid Cloud Compute Engine for a Build, then a Task if the Build succeeds. The card stays on the Repositories page while the run is in flight, and the result panel opens from the same card once the run finishes.
The run uses the per-repository configuration stored on the card, namely the branch, the execution core, the build directory, the command-line arguments, and any mounted data sources. A repository can also ship a signaloid.yaml file at its root to declare a minimum required core configuration, and the card warns when the active core falls below it.
Build and Task sequence
A Run proceeds in four steps:
- The platform submits a Build to the Signaloid Cloud Compute Engine.
- The Compute Engine clones the repository at the selected branch and builds from the configured build directory.
- Once the Build succeeds, the platform launches a Task on the active core with the configured command-line arguments and mounted data sources.
- The Compute Engine streams Build and Task output back to the platform.
Status bar and cancellation
While the run is in flight, a bar on the card reports the Build and the Task, each with its ID, its current status, and Cancel. Canceling one does not cancel the other. If either side ends in a remote error, the card surfaces the error message inline below the bar.
Every Build and Task you run on a connected repository persists in your account and shows up in Builds and Tasks.
Result panel
The result panel below the status bar carries the same four tabs as the Results Panel. Its Build tab holds the build log the Compute Engine returned for this repository.
Once a run has terminated, Open Execution Log () on the card opens a dialog with the same four tabs, so you can revisit the latest output later without leaving the Repositories page. The same dialog opens on its own whenever a Task or Build terminates without being canceled.
stdout, stderr, Build, and Runtime Information tabs.Variable discovery
Discover Variables () on a connected repository card opens
the Variable Viewer page for that repository at /repositories/detail.
Variable tracing works only on a Reference core, which you pick with the
execution core
button on the card.
On the Variable Viewer page, Discover populates the list of variables the platform can trace from your repository source. If the active core is not a Reference core, a banner offers to switch to a compatible Reference core in one click.
A repository can pre-declare the variables to trace by shipping a signaloid.yaml file at its root, so you do not need to pick them on every run.