Atlassian Bamboo vs. VMware Cloud Foundation

If you value integration over cost, Bamboo is clearly the way to go. It offers tight integration to the rest of the Atlassian suite, and when you need traceability from issue to build, Atlassian is the right way to go. However, if you find yourself needing to save on costs, you may consider taking an approach of rolling your own build system with open source alternatives, such as Jenkins, if you don't [mind] putting in a little extra elbow grease.

Incentivized

It is best suited for an on-premise cloud solution where customer can shift their entire production environment. Also, the customer has a preference for a Homogenous Infrastructure Environment where budget is not a challenge. It is not at all suited for a Heterogenous Environment, e.g., a Public cloud where integration becomes a huge issue, also in SMB sections where budget is challenging.

Incentivized

• Levels of granularity. Organization has many projects that have many build plans that have many jobs that have many tasks, etc. And branch builds allow source control branches to be built separately.
• Versatility. I can use bamboo to manage my Java, node, or .NET build plans. I can use it to spin up Windows or Linux build agents, or install it on a Mac to build there as well.
• Bamboo integrates with other Atlassian products like Bitbucket, Stash, JIRA, etc. If a company commits to the entire Atlassian stack then work can be tracked through the whole development lifecycle which is really useful.

Incentivized

• Cloud enabled Solution.
• Support Container based Apps.
• Cost efficient.
• Supports both Public and Private Environments.

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

• The Deployment is complex.
• Recommended Number of Physical Nodes is three or more; with less than 3 Nodes, it becomes difficult to install V-SAN.
• Need for better integration. If we go on the public cloud, it is a huge challenge while integrate with an open source platform.
• Cost can be marginally reduced. SMB segments still prefer a separate license instead of VCF, or they postpone their purchase plans.

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

Bamboo is a fairly small product but having said that it was fairly easy to get assistance. Especially for the small to easy things. Anything large or fairly complex was an issue finding detailed answers for. This caused a lot of trial and error on our part to try to find a solution.

We selected Bamboo because its capabilities to integrate with other Atlassian products specially Jira Software, Bitbucket and in some useful scenarios with Confluence. Also, we found these pros important for us: great user interface, easily agent deployment, Docker compability, simply to maintain / manage, and straightforwardly integration with different notification platforms

Incentivized

Although the public Cloud Model follows Opex Costing Model, it actually leads to very high costs also, the infra model in my organization is not suited for a Public Cloud Model. Hence We decided on an On-Premise Model, and the best suited was VMware Cloud Foundation, which is a complete Software-Defined Scale-Out Architecture. I also prefer a Homogenous environment; i.e, support and services from a Single OEM, so that I Can get faster resolutions to my tickets raised.

Incentivized

• It helped us achieve the Continuous Deployment and Continuous Integration goals for our applications, a huge milestone that saved a lot of time for developers in making the builds and deployments and saved time for QA in running the automated tests.
• Helped with DevOps: we moved the formal approval from the email to the system and allowed the approver to actually push the button for the production deployments.
• Biggest positive impact of using Bamboo is that it improved our response time to customers and increased the frequency of our deliveries to them.

Incentivized

• My organization has a size of 1300+ employees, using multiple applications and an exchange mail server that is hosted on On-Premise Cloud, hence scalability has not been a challenge.
• Having hosted my Production environment and Mail exchange Server on VCF, there has been optimum resource utilization with very little scope downtime. Hence have been able to save a lot of funds on Hardware resources.
• Due to the size of my organization and due the data load, I have been able to save on Resource Utilization and Organization Funds

Incentivized