Atlassian Bamboo vs. AWS CodeBuild

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

It is really good for building projects in the cloud. If you try to do build the project first locally and then push that stack to the cloud it could take a lot of time. In this way, it also consumes a lot of resources in the computer and in the network.

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

• Customization
• Do code builds within a schedule or when the source code changes
• Only pay for the build time used

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

• It was difficult to create a branching strategy with GitHub. We had everything running from main, but in a true devops environment, we would like to incorporate a true branching strategy.
• I would like to share build projects with each AWS account we utilize versus creating a build project in each account. It will allow us consistent deployments across the board.
• The error logs are natively in AWS, but when developers do not have access, there is no way for them to view error logs for maintenance other than an admin who has access to share the error logs.

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

It is a highly usable, well integrated CI/CD service, patricularly for AWS-centric organizations. It is a strong balance between simplicity and flexibility. Security was integrated with AWS Secrets Manager allowing secrets to be retrieved dynamically - a huge usability win for us. I did not enjoy the manual build for each environment

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

I've used GitHub Actions compared to AWS CodeBuild - I enjoyed the integration with AWS from a codebuild perspective, but GitHub Actions and Workflows allowed us to create a reusable pipeline which is more in line with our devops structure. I enjoy AWS CodeBuild, but from a true continuous deployment, GitHub Actions was more fit.

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

• AWS CodeBuild was introduces as a core enabler for automating database deployments and enforcing a standardization across six environments. The standardization and quality control was well received.
• Security was baked in reducing audit findings.
• Deployments took minutes to update all environments compared to hours. It helped us a lot to reduce drift and deploy consistently.

Incentivized