Atlassian Bamboo vs. Codefresh

Large companies will find it particularly useful, but smaller companies and independent developers will not be able to afford the cost, and will not see many advantages compared to using an open source solution. However, having some software to handle continuous integration build servers as well as deployments, and doing this consistently between products, is absolutely essential.

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

• Continuous Deployment - you can use Bamboo to automatically build and deploy whenever there are changes in the source code.
• Continuous Integration - by integrating the automated tests and the integration tests before deploying you make sure you know immediately if the latest code fits into the whole scheme of apps.
• Integration with Jira and Bitbucket.
• Flexibility with the program language used for builds: Maven, Ant, PowerShell, any command line tools.

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

• Extremely hard barrier to entry for non-backend developers
• Blackbox makes it hard to customize functionality
• The inability to add features without breaking core functionality
• No cloud solution
• Tasks cannot be put in if/else statements
• No clear right way to form build plans

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

Bamboo offers solid usability for teams looking for an integrated, scalable CI/CD solution, especially those using Atlassian tools. Its interface is intuitive for existing Atlassian users, and its focus on deployment automation makes it a strong option for continuous delivery. However, its complexity and cost may pose challenges for small teams or those new to CI/CD. Overall, Bamboo’s usability shines in environments where ease of integration and streamlined workflows are prioritized. Still, it may require more effort for teams unfamiliar with its setup or without dedicated resources.

Incentivized

Support for Bamboo has started lack a little over the years. Atlassian has been moving more towards Bitbucket Pipelines and away from the on-premise install of Bamboo. While the tool is still great, it may take a little bit of time to get a question answered by official support.

We chose Bamboo over Jenkins for 2 reasons - one, for its tight integration amongst all the products in the tool suite. We find explicit value in the traceability from JIRA issues all the way down to the Bamboo build that was triggered by the check in of those issues. The second reason was for support - we didn't want the burden of figuring out how to support Jenkins in our production environment, as can be the case with so many open source products.

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

• Bamboo was neither very positive or negative. Most of our spend was in man hours on research and development
• We felt it was worth it for larger projects
• Smaller projects had too much setup and run and caused a negative ROI

• 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