Senior DevOps Engineer at a transportation company with 10,001+ employees
Real User
Top 20
Sep 16, 2026
Codefresh serves as the continuous integration tool in our GitOps principle deployment strategy, while we use Argo CD for deployment. Codefresh handles building, testing, and running test cases. When a change request is approved by the product team, developers push code that automatically triggers Codefresh for that specific branch. Codefresh checks out the code, runs unit and integration tests, then builds the Docker image. A recent scenario where Codefresh failed involved one of our test cases. Codefresh properly failed the pipeline to ensure that code being pushed meets the highest quality standards and security gates. Other special gates are attached to the pipeline, such as SonarQube analysis. Codefresh ensures we are able to pass these fixes, and at the very least, it serves as our build tool. The container-native pipeline and the handoff to Argo CD is quite unique.
Senior Engineer at a insurance company with 1,001-5,000 employees
Real User
Top 5
Jul 23, 2026
My main use case for Codefresh is continuous integration and delivery. I use Codefresh for continuous integration and delivery in my workflow by using CI/CD pipelines to trigger builds for code and deployments.
My main use case for Codefresh is establishing environments for critical operations and creating a self-service process in Argo CD, providing infrastructure and resources and other types of resources using Crossplane, and syncing on a repository through GitOps on Argo CD.
My main use case for Codefresh is for build and release. For build and release with Codefresh, we maintain the version-controlled file of the pipeline. Once a commit happens, the build will trigger for that commit on that branch through a pull request. It will build the artifact, scan a few images in Docker, then put the artifact registry image in a remote registry, and then publish the deployed artifact to the deployed environment.
I use Codefresh for Kubernetes applications and to deploy Kubernetes applications. We have used Codefresh for deploying containerized applications to Kubernetes environments, and our organization has adopted GitOps for managing multiple environments such as development, staging, and production, which makes Codefresh ideal for this purpose. Managing the Kubernetes platform and deploying applications on Kubernetes is very difficult, but Codefresh has made it easy to deploy applications in different environments like production, staging, and development.
Codefresh is a progressive tool tailored for enhancing DevOps teams, enabling swift deployments with its Kubernetes-native architecture while supporting GitOps control to provide a centralized view of Argo CD runtimes and clusters.Codefresh stands out by integrating real-time application health monitoring, efficient artifact management, and smart deployment strategies. Automation features reduce manual efforts allowing seamless version control integration. While users appreciate its...
Codefresh serves as the continuous integration tool in our GitOps principle deployment strategy, while we use Argo CD for deployment. Codefresh handles building, testing, and running test cases. When a change request is approved by the product team, developers push code that automatically triggers Codefresh for that specific branch. Codefresh checks out the code, runs unit and integration tests, then builds the Docker image. A recent scenario where Codefresh failed involved one of our test cases. Codefresh properly failed the pipeline to ensure that code being pushed meets the highest quality standards and security gates. Other special gates are attached to the pipeline, such as SonarQube analysis. Codefresh ensures we are able to pass these fixes, and at the very least, it serves as our build tool. The container-native pipeline and the handoff to Argo CD is quite unique.
My main use case for Codefresh is continuous integration and delivery. I use Codefresh for continuous integration and delivery in my workflow by using CI/CD pipelines to trigger builds for code and deployments.
My main use case for Codefresh is establishing environments for critical operations and creating a self-service process in Argo CD, providing infrastructure and resources and other types of resources using Crossplane, and syncing on a repository through GitOps on Argo CD.
My main use case for Codefresh is for build and release. For build and release with Codefresh, we maintain the version-controlled file of the pipeline. Once a commit happens, the build will trigger for that commit on that branch through a pull request. It will build the artifact, scan a few images in Docker, then put the artifact registry image in a remote registry, and then publish the deployed artifact to the deployed environment.
I use Codefresh for Kubernetes applications and to deploy Kubernetes applications. We have used Codefresh for deploying containerized applications to Kubernetes environments, and our organization has adopted GitOps for managing multiple environments such as development, staging, and production, which makes Codefresh ideal for this purpose. Managing the Kubernetes platform and deploying applications on Kubernetes is very difficult, but Codefresh has made it easy to deploy applications in different environments like production, staging, and development.