Cyclid was built to make testing easier – so it’s no surprise that we’re equally easy to work with.
It’s designed to be flexible, so you can add the functionality you need, and leave out what you don’t. What’s more, the same determination to understand and solve your CI problems also powers our support.
Cyclid grew from our belief that CI could be done better – and be more user-friendly. As developers, we’ve designed the kind of system that we’d want to use ourselves.
Cyclid jobs are written in either YAML or JSON. They are composable so you can share common Stages between your jobs.
Every job is run in it’s own Build host, and every Build host is ephemeral. Cyclid is agentless so there’s no need for any dedicated, long running instances. Build hosts are only created when you run a job, saving your resources and money.
Plugins are lightweight and easy to write in Ruby.
Cyclid is designed to be a horizontally scalable with a share nothing design. All it needs is a database.