CloudBees CI vs Hydra

CloudBees CI is a centrally managed Jenkins environment for teams delivering continuous integration at scale. It can run on-premise or in the public cloud, with a modern cloud platform designed for Kubernetes and a traditional platform edition. Operations Center provides a central view across CI controllers. Pipeline capabilities include complex delivery pipelines, declarative syntax, and builds that can survive controller and agent failures. The CloudBees Assurance Program vets plugins, while Beekeeper helps administrators monitor and manage plugin upgrades. Documented integrations include GitHub and Bitbucket, plus Slack and Microsoft Teams. Security options include central management, role-based access control, single sign-on, and connections to external credential stores such as CyberArk and HashiCorp Vault. CloudBees CI is paid, with pricing available on request, and has no free plan. 24/7 expert support depends on the customer’s support agreement. CloudBees support policies cover only CloudBees-certified plugins on services based on Jenkins core.

Hydra is a continuous integration service for projects based on Nix. It checks out project source periodically or continuously, builds it, runs tests, and produces reports. Work is organized into jobsets whose inputs can trigger builds when they change; jobsets can also depend on one another. Flake jobsets are supported when their outputs expose a hydraJobs attribute set. Jobs can produce packages, ISO images, or tarballs, and jobset inputs can use Git checkout sources. Hydra also provides a JSON API. It is aimed at Nix and NixOS package developers, not people who only need to use NixOS. Hydra is open source under GPL-3.0 and listed at free. It is self-hosted, with no hosted option listed, and running it is currently supported only on NixOS; the repository recommends the NixOS module for production. Flake evaluation is restricted from accessing files outside the Nix store. Some state is stored in the database, so backups are needed, and the wiki reports that hydra-queue-runner can sometimes leave queued builds unscheduled.