What it does
Codefresh CI connects source repositories to container-based build and test steps. Teams can compose pipelines with reusable triggers, parallel execution, shared volumes, caching, and pipeline debugging, then select SaaS, hybrid, or on-prem builders. It focuses on the continuous-integration stage of a container delivery workflow.
Build and test the image
The documented quickstart connects a repository, builds its Docker image, runs unit tests against that image, and stores the result in a registry. Pushing to Docker Hub is an optional step. This is a useful starting shape for a service that already has a Dockerfile: keep build and test steps together, then extend the pipeline with its own packaging or release actions.
Codefresh's product page describes reusable triggers, shared volumes, caching, parallel steps, and live debugging for teams that need to tune multi-step builds. Octopus confirms that Codefresh CI remains supported after its acquisition, while the former Codefresh GitOps Cloud is no longer available. The CI page directs prospective buyers to contact the team, and the pages reviewed do not publish current plan limits or paid pricing.
Strengths
- The quickstart covers a container build, tests against the image, and storage in a registry.
- Reusable triggers, shared volumes, caching, and parallel steps support multi-stage pipeline design.
- The product page describes SaaS, hybrid, and on-prem builder options.
Best for
- Teams building and testing container images in CI
- Services that need reusable pipeline steps across multiple repositories
- Organizations evaluating SaaS, hybrid, or on-prem build infrastructure
Sources
- Awaken the power of modern CI with Codefresh CI (Oct 26, 2026)
- Codefresh and Octopus Deploy (Oct 26, 2026)
- Pipeline quick start · Codefresh | Docs (Oct 26, 2026)