Zont

Sign in

Enter the CI Workspace ID and Workspace Secret. Accepted credentials stay in this browser's localStorage until you log out.

About Zont

Jobs overview

Controller unknown
0 queued 0 running 0Jobs 0 / 0Passed 0 decided of 0 recent builds

Queued

Queue empty - no queued jobs

Showing oldest 0 of 0 queued jobs.

StatusJobOriginRequested
No queued jobs.

Active

Idle - no active jobs
StatusJobOrigin CommitMessage StartedElapsed
No active jobs.

Completed

ResultJobPackage versionCommit MessageFinished
Loading...
How jobs, logs, and controls work

Queued jobs shows the bounded durable pending spool oldest-accepted-first and explicitly reports when more rows exist; Active jobs shows every currently running job from a telemetry-enabled Lifub runner. Origin identifies the console, CLI, Git-push, or schedule entry path, not a person: the shared workspace credentials do not provide human identity. Both live tables are read-only; ordinary queued or running requests retain the existing Cancel control in Jobs, while ci-redeploy remains protected.

The completed table starts with the fifty newest jobs matching the filter; use Duration to order that window shortest-first or longest-first. Every runner build keeps its full console output as an audit log next to the telemetry. Any linked job name jumps to its current checked-in declaration below, a commit opens its repository entry, and a linked Finished timestamp opens that exact audit log. Click a package version or message to show it in full and select it, then copy it with Ctrl/Cmd + C; the console never reads or writes your clipboard, so no browser permission is involved. Result icons and durations are deliberately not copy controls. Navigate with j/k, open a log with Enter, and press ? for all shortcuts.

Repository

CommitMessage AuthorWhen
Loading...

Execution workers

Loading...
WorkerPlatform CapabilitiesState
Loading...

Checkout worktrees

Loading...
PathLane CommitState
Loading...

Remote Rust worktrees

Loading...
RepositoryReserved ref CommitState
Loading...

Branches and commits are read from the runner's managed checkout - the exact repository state CI builds from, not a hosting provider's view. Pick a branch from the dropdown; main is fetched by the watcher about once a minute, while other branches update when the runner re-fetches them, so each branch option's tooltip names when its tip last moved. The view is read-only; click a commit or message to show it in full and select it for copying. Execution worker rows show sanitized enrollment and heartbeat state. Remote Rust rows expose only repositories admitted by checked-in policy plus their sanitized reserved refs and worktree lifecycle - never credentials, lease tokens, commands, remotes supplied by a caller, or host paths.

Container registry

Loading...
RepositoryTag DigestUpdated
Loading...

This authenticated, read-only view comes from a bounded stable scan of the local oci.lifub.com Distribution v2 tag pointers. Updated is the tag pointer's filesystem timestamp, not the image build time. Exact totals, truncation, scan age, staleness, and errors are reported above. Registry credentials, users, manifests, blobs, uploads, and filesystem paths are never exposed.

Jobs

Repository-relative path-prefix and interval trigger details come from each checked-in build definition. Run immediately queues the displayed fixed manual recipe; while that request is queued or running, the same control becomes Cancel. Manual controls cannot supply artifacts, environment variables, custom arguments, retries, or arbitrary deployment targets. Jobs marked Typed request use their dedicated authenticated CI tool and never expose the generic Run control; acli-release remains available through ci_release_acli(version) or just acli-release VERSION. The fixed ci-redeploy recipe remains runnable when listed, but its rollout and rollback transition is protected from cancellation.