Buildkite vs. Codefresh

I would definitely recommend Buildkite for anyone who needs a decent CI solution for 50+ on AWS instance without paying huge amount for AWS Build and code deploy tools.

Incentivized

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

Incentivized

• CI Solution
• Notification
• Configuration

Incentivized

• 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.

Incentivized

• Integration can be improved
• Cost reporting can be impoved

Incentivized

• 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

Incentivized

Buildkite was easy to use and setup while comparing Circle CI or GitHub. Additionally Buildkite was very affordable for teams while comparing GitHub plans

Incentivized

It's very scalable It is cost effective It easily get integrated with third party tools It easily get integrated with Kubernetes Docker.

Incentivized

• Faster Build time
• Increased productivity

Incentivized

• Positive:
• As an Automation tools I must say it has reduced manual labour , reduced errors and improved quality of work.
• It easily get integrated with third party tools which increases ease ness in our work
• Negative:
• Although being a very good tools in CI/CD
• It requires improvement in UI, it's speed, security, optimization.

Incentivized