We performed a comparison between AWS CodePipeline and Bamboo based on real PeerSpot user reviews.
Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The tool's recent version helps us to run pipelines in parallel. The integration with other AWS services has greatly impacted our use of AWS CodePipeline. It made tasks such as integrating with Jira and provisioning instances much easier."
"The product is a one-stop solution that you can use to integrate, deploy and host your application."
"In AWS, the Cloud DevOps is a managed service from CodeCommit and this has removed the need for a lot of manual steps."
"It helps develop CI/CD implementations with centralized management of code building, deployment, and version control."
"The product is cost-effective and integrates well with the AWS environment."
"It's a perfect solution if you are just using AWS."
"The integration with other applications is fabulous."
"AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing."
"The platform helps us with automated and timely backup. It provides data replication as well."
"One of the significant benefits of Bamboo is its built-in support for numerous clients and the ability to tailor its capabilities to your specific requirements. This high level of customization enables you to create pipelines that are ideally suited to your needs, making it an invaluable tool for conducting advanced testing."
"It's one of the best solutions in this line of work. We have many Atlassian products. We use Bamboo, JIRA, Service Desk, and some other Atlassian plugins. We like that it's easy to integrate into each other. It's a suite of services."
"The most useful feature of Bamboo is its integration with other solutions such as Jira and BitBucket, also offered by Atlassian. It is easier to use tools all provided by one vendor."
"The most valuable features are compiling and deployment."
"In Bamboo, build and deployment have been segregated. The build plan and deployment plan are different. When comparing Bamboo to other solutions, the native feature you will not find in another tool, such as Jenkins. They have segregated the build and deployment plan. This means, building the application and deploying it are two separate parts in Bamboo, they have segregated it apart from the UI. This makes the tool a bit better compared to other tools."
"Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process."
"The most valuable features of Bamboo are its performance and UI. Additionally, there are a lot of useful plugins, integration with other solutions, such as Bitbucket and Jira, and a helpful online community."
"AWS CodePipeline doesn't offer much room for customization."
"In the next release, I would like to see fewer timeout errors."
"The migration process from one source code to another needs improvement."
"The solution could improve the documentation. Sometimes we have some issues with the documentation not updating after releasing .NET 6. We had some issues with building the code pipeline, and it was not updating the documentation. It's better to update the code documentation."
"If you're talking about multi-cloud, you can't use it."
"It would be a much better tool if it could be made compatible with other cloud services as well since this is an area the product currently lacks."
"If there are many dependancies involved in the setup, it may take a long time."
"The tool does not provide automated features for evidence collection."
"The performance around the deployment feature could be improved."
"The solution needs to support more customization in the training. What's offered is pretty generic. They need better training and should offer more guidance."
"Bamboo is a bit complicated to use compared to other solutions, such as GitLab. You have to integrate different actions that are difficult that could be made easier."
"Bamboo can improve by providing more with scripting, such as they have with Jenkins. Bamboo is more UI-driven at this time, Jenkins is going in that direction too."
"It would be great if Bamboo could introduce a more containerized deployment model."
"One area that could be enhanced is the governance process, particularly with regard to building approvals and transitions between stages. In comparison to other solutions, such as Jira, which features a workflow that supports approval processes, this capability is not natively available in Bamboo. To implement this functionality, integration with other solutions, such as GSM may be necessary. Although some add-ons, such as Adaptavist ScriptRunner, are available in the market to circumvent this limitation, they may not offer the exact functionality needed. Therefore, there is certainly room for improvement in this area."
"It should be much easier to use. It shouldn't require a lot of reading to be able to use it. It should have just two or three screens rather than hundreds of screens requiring a lot of clicking. It also requires a lot of integration. It has a steep learning curve. It takes a lot of time to understand and put in the data. There is also no proper training."
"The marketing strategy of Bamboo is an area of concern where improvements are needed."
AWS CodePipeline is ranked 3rd in Build Automation with 13 reviews while Bamboo is ranked 5th in Build Automation with 20 reviews. AWS CodePipeline is rated 8.4, while Bamboo is rated 7.4. The top reviewer of AWS CodePipeline writes "A fully managed service with excellent integrations and a flexible architecture". On the other hand, the top reviewer of Bamboo writes "High availability, helpful support, and plenty of plugins available". AWS CodePipeline is most compared with GitLab, AWS CodeStar, Jenkins, GitHub Actions and Harness, whereas Bamboo is most compared with GitLab, Jenkins, GitHub Actions, Harness and Microsoft Azure. See our AWS CodePipeline vs. Bamboo report.
See our list of best Build Automation vendors.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.