Conda
Conda CI on GitHub Actions
Environment solving takes longer than the analysis itself.
6m → 40s
Env solve
Environment solving takes longer than the analysis itself.
Why it happens
The classic conda solver is slow and the package cache is not persisted.
What to change
- Use mamba or the libmamba solver instead of the classic solver
- Cache ~/conda_pkgs_dir keyed on the environment file
- Pin the environment with an explicit lock file so solving is skipped entirely
Conda on runnerhut
yaml
jobs: test: runs-on: runnerhut-8vcpu-ubuntu-2404 steps: - uses: actions/checkout@v4 - uses: conda-incubator/setup-miniconda@v3 with: { miniforge-version: latest, use-mamba: true } - run: pytest -n autoThe only runnerhut-specific line is `runs-on: runnerhut-8vcpu-ubuntu-2404`. Everything else is standard GitHub Actions — the same actions, the same secrets and the same permissions model you use today.
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
Database migrationsEvery test run replays the full migration history from an empty database.dbtdbt parses the entire project and re-runs unchanged models.SparkSpark jobs in CI spend most of their time on JVM startup and jar assembly.AirflowDAG import checks reinstall the full Airflow dependency set each run.