Codefresh : Unleash Continuous Integration and Continuous Delivery
Rating: 7 out of 10
IncentivizedUse Cases and Deployment Scope
As a DevOps engineer I use Codefresh as an Automation Tools. Business problem like lot of manual intervention, human error, delaying deliveries etc are we experiencing in our organization before Codefresh. With Codefresh Now we can so lve all these problems. The scope can be found from small to mid and from mid to large size organisation. which is totally depends on organisational needs and requirements.
Pros
- Continuous Integration and Continuous Development. we can setup jobs that automatically triggered when there is any changes in code and starts building up the build images automatically and then pushing images to Container Registry
- We can involve Version control system like github, bitbucket, gitlab etc for integration of Codefresh with our code stored in these Version control systems.
- On the failure of any jobs/pipeline Codefresh can also send Notification on our email.
Cons
- With Codefresh it's become hard to handle complex pipelines
- Need to focus more on Documentation part
- UI can be more attractive
- Security can be more increased
Likelihood to Recommend
While deploying docker images on kubernetes pods I must say Codefresh helped me a lot.
It has made my work easy as an Automation tool.
I can setup a simple pipelines to automate my build for kubernetes.
but for more complex pipelines Codefresh need some improvement
It has made my work easy as an Automation tool.
I can setup a simple pipelines to automate my build for kubernetes.
but for more complex pipelines Codefresh need some improvement
ST
Shivangani Tamrakar
DevOps Engineer in Information Technology at SoluLab (51-200 employees)
Vetted Review
1 year of experience