Re:Radicle: Sovereign {code forge} built on Git
by stephbook on Friday May 15, 2026 @01:12PM
(#48151200)
I don't understand why you'd want them to built another CI system. Just for the sake of it?
Feels like using a free Jenkins gets you everything you want. Doesn't need more than a container or Java either.
Re:Radicle: Sovereign {code forge} built on Git
by jayd16 on Friday May 15, 2026 @01:53PM
(#48151690)
That's also perfectly fine if that's what it is. I would just phrase that as "They don't have CI but they provide hooks."
Re:Radicle: Sovereign {code forge} built on Git
by gsaslis on Friday May 15, 2026 @04:42PM
(#48153535)
it's a little of both: on the one hand we're working on CI integrations (through generic webhooks or CI-engine-specific adapters that basically implement the CI engine's API [1]), so you can keep on using your existing CI solution. On the other hand, yes, there is also work towards a new CI engine (Ambient
[2]), which aims to make it safe and secure to run CI on other people's code, which is important when working towards a distributed, community-ran, CI system. We should have more docs regarding the CI story up on radicle.dev in the next week or two.
[1] - https://radicle.network/nodes/index.radicle.garden/rad%3Az3G... , [2] - https://ambient.liw.fi/
Gitlab and Github have pages and pages going over the domain language used to configure the job triggers. Jobs can trigger other jobs either in response to completion or as a dependency etc etc.
I would say these radicle-ci designs as they are now are actually quite rudimentary. That's perfectly fine for an early project but at this point I think you have to say that they won't have a CI system ready for quite some time.