Hydra vs Travis CI
Hydra
github.com
Travis CI
travis-ci.comSide by side
| Figure | Hydra | Travis CI |
|---|---|---|
| Price from | Free | $63.25/mo |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | Yes | — |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 7 |
| Spec score · Continuous Integration Software | 8.5 (#11) | 8.0 (#27) |
| Integrations | Hydra jobset inputs can use Git checkout sources, and the documented examples use GitHub repositories. | The product page names GitHub, GitLab, and Bitbucket integrations and says it supports more than 40 CD providers. |
| Purpose | Hydra is a continuous integration service for Nix based projects. | Travis CI is a CI/CD service for automating software testing and deployment. |
Plans
Travis CI
- Free PlanFree
- 1 concurrent job Plan$69 a month
- 2 concurrent jobs Plan$129 a month
- 5 concurrent jobs Plan$249 a month
- 1 concurrent annual job Plan$759 a year
- 2 concurrent annual jobs Plan$1,419 a year
- 5 concurrent annual jobs Plan$2,739 a year
In their own words
Hydra
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.