Jobs
The Jobs tab on each repository shows CI results reported by external systems. Radish displays status, commit, runner, and log links — the actual build execution happens elsewhere.
What you see today
Open the Jobs tab on any repository. Each row represents a CI run reported against a specific commit and shows:
- Status indicator — a green checkmark (success), red cross (failure), or hollow circle (pending).
- Commit — the short OID linking to the commit detail page.
- Runner — which CI runner executed the job.
- Timestamp — when the result was reported (hover for exact UTC time).
- View Log — a link to the full build log on the external CI system, when available.
If no CI system has reported results, you'll see an empty state message.
How CI results get here
Radish does not run builds itself. It receives job reports from external CI systems that watch your Radicle repository for new commits and patches. These reports are stored in the format specified by radicle-job. The most common way to wire this up is with radicle-ci-broker.
Setting up radicle-ci-broker
radicle-ci-broker is a daemon that listens for events on a Radicle node and dispatches CI jobs to an adapter of your choice. It then reports results back so they appear in the Jobs tab.
How it works
- The broker subscribes to your Radicle node's event stream.
- When a new patch or push arrives, it triggers the configured adapter.
- The adapter runs the build (or delegates to an external system) and reports success or failure.
- The broker writes the result back as a CI status on the relevant commit.
Adapters
radicle-ci-broker supports various adapters for different CI backends, such as Concourse and Ambient. Each adapter is configured through the broker's configuration file. Refer to the radicle-ci-broker repository for full setup instructions and adapter-specific options.
Minimal setup
- Install radicle-ci-broker alongside your Radicle node.
- Choose an adapter and configure it in the broker config file.
- Start the broker daemon — it will begin watching for events immediately.
- Push a commit or open a patch; the Jobs tab should update once the build starts.
Hosted Radish Jobs (coming soon)
In a future release, Radish will offer hosted CI — build execution managed directly by the Radish instance, with no external broker or adapter setup required. You'll be able to define build steps in your repository and have them run automatically on every patch or push, with results appearing in the Jobs tab as they do today.
Until then, hosting your own radicle-ci-broker is the recommended path for CI on Radicle repositories.