Atlassian Bamboo vs. Hudson CI (discontinued)

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

Though it has a few setup issues, once you are done with setup it works like charm so one time setup issues won't bother. Reporting, version tracking, debugging everything is helpful and more clear and it reduces effort, in our scenario our QA team integrated their script with Hudson so that after every release it will get triggered automatically and developers will know if there is any major issue.

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

• Oracle Hudson UI provides a simple setup and integration with SVN and other version control tools.
• The user control provides various operations to users through which it's easy to control the CI deployment process.
• It handles Performance testing and Automation testing, provides and accepts user interaction. Allows them to schedule jobs

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 setup needs to be more user friendly, currently for first time users CI doesn't provide more guidelines.
• JMeter tool can be integrated but it's not easy, user has to follow and do research before setup. A simpler way would help make the process more user friendly.
• Selenium tool like JMeter can be integrated, if its Webservice it's easy but for UI automation integration not enough information is provided.

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

Oracle CI in terms of setup lags behind all above products, but then its use is also limited to release management so we can't really compare. Majority of organizations have dedicated team to help with CI Process so they take care of managing all jobs and setup.

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

• Provides an easy way to deployment process
• Centralizes control for all release management
• Secured process, a user can only check errors and release management can take control of deployment. User roles are provided.

Incentivized