Webhooks in radicle.garden
Webhooks let your Radicle Garden node notify external services when a push or patch lands on one of its repositories — typical use is triggering a CI build, posting to chat, or feeding events into your own backend.
Two ways to manage webhooks
-
In the dashboard (recommended) — create, edit, and inspect webhooks from your browser, with no CLI or local key required. This is the easiest way to get started and the best place to debug deliveries.
-
With the
rad webhooksCLI (alternative) — manage webhook configuration from a repo working copy. Useful for scripting or infrastructure-as-code.
Both methods configure the same webhook delivery on your Garden node, so pick whichever fits your workflow.
Guides
Pick your guide, depending on what you want to achieve:
-
Getting Started with Webhooks — Create a webhook in the dashboard and verify it fires, using webhook.site as a dummy receiver. 5-minute smoke test. Recommended starting point.
-
Manage Webhooks from the CLI — The same setup from a repo working copy with
rad webhooks, for scripting or infrastructure-as-code. -
Trigger CI runs on your Jenkins — End-to-end Jenkins example: receive webhooks, run a pipeline, post commit status back.
We Need Your Feedback
This is a new feature aimed to help you integrate with existing CI solutions, while we’re busy working on a hosted CI solution! As a new feature, there may still be some rough edges and we would love to have your feedback!
Reach out to us on zulip for any issues you encounter, or if you have any questions.
rad webhooks , for scripting or infrastructure-as-code.