Codefresh Reviews

Documentation about GitOps and Certification lab about GitOps.

no , all contents are fine for the purpose of certification

It solves the problem of understanding GitOps concept

Codefresh is pretty simple to use and can easily handle some of our more resource intensive pipelines

I can't think of any downsides at the moment

Currently we use Codefresh as a CICD platform for delivering software to all of our environments

the integrations tool, like github actions, jenkins and security tools like snyk, easy setup using webUI with a couple of clicks and gather better stats from your deployments.

progressively more tools are going to integrate into this interface, I would like a good idea to integrate all CLIs in one tool like aws-cli, to manage your confs on your cloud-hosted session, argocd and argo workflows in all in one cli binary.

for all users is a good choice to integrate some tools all in one UI with the gitops culture and stats, for us DORA is good idea for the devops team to leverage to improve our daily tasks.

The ease of use, setup, and simple integration with our AWS ECR Docker containers. Deployment is simplified across our environments.

So far everything has worked very well, no dislikes to mention at this time.

The only question we have might be cost vs Github Actions.

Simple Git Ops type of flow that allows us to deploy when we push to specific branches and also allows steps for approval before deployment is triggered.

Apart from a stunning and easy to use UI and packed with tons of features, we liked how Codefresh works with containerization and Kubernetes in mind. Another helpful capability was the ability to define custom steps that can be reused in numerous pipelines. That significantly simplifies building custom pipelines (especially if following GitOps like pattern).

Even though Codefresh was very well documented, we also got tremendous help from support. The team was very responsive, both for the free and paid plans.

Hard to answer. Codefresh was the choice for CI/CD pipelines for two of my projects.

Definitely worth a try! Works well for us.

Running end-to-end CI/CD pipeline to build, run automation tests, deploy product versions.

All the integrations are really easy to do, at the moment I'm the only one working on Codefresh and it was not hard at all to implement everything by myselfc everything is well documented.

Terraform provider is a little outdated, that's my only point, I can't create everything I want using terraform itself, I think codefresh should invest a little bit of time working on that one.

Basically we needed to do CI/CD pipelines from scratch and fast and Codefresh really solved all our issues with that, now we feel more productive and the deployments increased dramatically

UI is very simple and informative. integration to cloud is also simple

I am pretty happy with the service compared to the alternatives

Continous integration and deployment is simplified.

Yes it is financially beneficial ,

Yes, its productive.

The best part of Codefresh is the declarative definition of pipeline templates and pipelines specification, either via native Codefresh resource or via Terraform, and the reusability of pipeline templates across multiple repositories.

Documentation is precise and helpful. The support from Codefresh team is also great.

The only thing which I dislike about Codefresh is pricing. We have around 200 users and pay per seat plan is quite expensive.

I would highly recommend using Codefresh, both for personal projects and for businesses at almost any scale.

We have unified CI/CD process for more than 70 repositories. Now developers bind their repository to one of the pre-made pipelines by the SRE team.

I love that Codefresh is so flexible and able to do whatever I need it to.

The UI is pretty nice to use, but there a few options that could be a little easier to find/use.

Codefresh helps us to not only deploy to a Kubernetes cluster, but to automate it with great visibility into the deployment process.

The Kubernetes first-class integration makes it easier to adopt a "per branch" continuous delivery deployment. This powerful feature can be leveraged together with the templating features and pipeline variables to really standardize and simplify CI/CD across an organisation.

Although it is possible to create triggers for the pipelines from the UI, triggers are a relevant part of CI/CD pipelines configuration and they should be defined as code and versioned as well.

If you are looking for a Kubernetes-first platform to build your CI/CD strategy, Codefresh is a great tool, especially if you are looking to adopt GitOps methodology. If you are not embracing microservices and Kubernetes, you might opt for a different CI/CD tool with a different or a more general focus: although Codefresh is flexible and can be used for most CI/CD pipelines use cases, their focus is clearly on K8 and microservices and I expect them to always prioritize features on their roadmap that are mostly useful for developers that use these technologies and architectural approaches.

Our goal was to have full CI/CD pipelines which integrates easily with several Kubernetes cluster, as well as the possibility of run automated tests in a docker-compose like setup. Thanks to Codefresh, our testing strategy has become more flexible: we didn't have anymore to mock all external services, such as databases or message brokers, for testing purposes, but we could selectively decide which ones to mock and which ones to run in a docker-compose during pipeline execution