CI/Build Infrastructure

Eidetica uses a CI/build system with GitHub Actions, Forgejo CI, and Nix flakes.

The philosophy for CI is that compute resources are cheap and developer resources (my time) are expensive. CI is used for comprehensive testing, status reporting, security checks, dependency updates, documentation generation, and releasing. In the current setup some of these are run multiple times on several platforms to ensure compatibility and reliability across different environments.

Fuzz / simulation testing are planned for the future.

CI Systems

GitHub Actions

The primary CI runs on GitHub with these workflows:

• rust.yml: Main Rust CI pipeline (format, clippy, build, test, doc tests, book tests)
• nix.yml: Nix-based CI that mostly runs the same tests but inside the Nix sandbox
• security.yml: Weekly vulnerability scanning and dependency review
• coverage.yml: Code coverage tracking via Codecov
• deploy-docs.yml: Documentation deployment to GitHub Pages
• release-plz.yml: Automated releases and crates.io publishing

Forgejo CI

A dedicated Forgejo runner provides CI redundancy on Codeberg. The Forgejo workflows mirror the testing in the GitHub Actions setup with minor adaptations for the Forgejo environment.

Nix Flake

The Nix flake defines reproducible builds and CI checks that run identically locally and in CI:

• nix build - Build the default package
• nix flake check - Run all CI checks (audit, clippy, doc, test, etc.)

Binary caching via Cachix speeds up builds by providing pre-built dependencies.

For local development setup, see Contributing.