Radicle CI

Radicle CI add continuous integration (CI) support on top of Radicle. There are several components:

• The CI broker receives change events from the Radicle node and triggers CI to run based on its configuration.

• An adapter is invoked by the CI broker to use a CI system to run CI for a specific change. There are several adapters, each for a different type of CI system.

• A rad-ci extension for the Radicle rad command emulates a CI run by running it locally. This avoids having to wait for a CI node ("server") to have free resources.

Updates and newsletter

See radicle tag on my blog for updates from me about Radicle and Radicle CI. Most importantly, a monthly newsletter.

Support

• The Radicle Zulip has a #radicle-ci channel where you can ask and discuss anything related to Radicle CI. That Zulip is the go-to place for all Radicle related issues.

• CI office hours are a weekly time to ask questions or discuss anything related to Radicle CI, on a video call.

  • Fridays, alternating between 8:00 and 17:00 UTC
  • see Zulip (#radicle-ci channel) for weeks and updates
  • https://meet.ffmuc.net/radicleciofficehour (Jitsi, works well in browsers)

Documentation for the CI broker

• Overview
• Architecture
• User guide
• Acceptance criteria
• Implementing an event filter
• Implementing an adapter

Documentation for the Ambient adapter

Ambient is a CI engine that makes it safe and secure to run CI for untrusted code.

• Ambient CI engine
• adapter for Ambient

Source code repositories

• This Radicle CI home page
• CI broker
  • the README.md has links to many adapters
• Ambient CI and adapter for Ambient
• The native CI adapter for running CI locally on the CI host, for trusted code
• rad-ci