4 ms·

radicle is pretty neat, i'd be quite curious to read more about the state of CI and moderation (given the P2P nature).

• lorenzleutgeb 8mo ago
  For CI, please refer to https://radicle-ci.liw.fi/ https://radicle-ci.liw.fi/ and https://radicle.xyz/2025/07/23/using-radicle-ci-for-development https://radicle.xyz/2025/07/23/using-radicle-ci-for-developm...
• 0x3o3 8mo ago
  for the state of Radicle CI read this post from the maintainers https://blog.liw.fi/posts/2026/radicle-status-quo-01/ https://blog.liw.fi/posts/2026/radicle-status-quo-01/
• iamnothere 8mo ago
  Re: moderation: Like BitTorrent, you choose which repos to mirror. If you’re crazy or you watch your server like a hawk you could just choose to automatically mirror everything. Like BitTorrent there is no way to “moderate” what another node chooses to share. They are working on tools to help permissive nodes remove repos flagged for deletion, but the protocol itself does not prevent a node from ignoring this flag.
• kitplummer 8mo ago
  I had a few different issues getting the CI broker working the way I wanted to (don't even remember what the issues were, but it had to do with catching patches) so wired up my own way but simply polling via Git - using a thing I built a while back called goa (gitops agent) for another project. The tricky part was getting the output from what ever do with the code, back into the Radicle patch. But it works. https://revolveteam.com/blog/goa-radicle-ci/ https://revolveteam.com/blog/goa-radicle-ci/ There are some caveats - mostly security related - given this is potentially executing commands on a host node.