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."It helps develop CI/CD implementations with centralized management of code building, deployment, and version control."
"Code deployment is the best feature."
"The most valuable feature of AWS CodePipeline is the flexibility of the configuration."
"The integrations are good."
"I find performance to be the most valuable CodePipeline feature. It works perfectly and smoothly."
"AWS CodePipeline has valuable integration features."
"AWS CodePipeline offers multiple integrations and it has its own set of features in the area of code scanning and dynamic code testing."
"The product is a one-stop solution that you can use to integrate, deploy and host your application."
"The most valuable features are compiling and deployment."
"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."
"One of the big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system."
"In my experience Bamboo is scalable."
"The most valuable feature of Bamboo is that it is a good tool for CI/CD integration."
"It can do the CI pipeline well."
"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."
"The platform helps us with automated and timely backup. It provides data replication as well."
"The migration process from one source code to another needs improvement."
"In the next release, I would like to see fewer timeout errors."
"There could be a possibility of deploying tag-based conditions for different environments using the same code base."
"The product’s pricing needs improvement."
"If you're talking about multi-cloud, you can't use it."
"If there are many dependancies involved in the setup, it may take a long time."
"The setup time is a bit long."
"The support team’s response time must be improved."
"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 can be challenging for someone new to the system or ecosystem to grasp, making it difficult to train new people and help them understand."
"The marketing strategy of Bamboo is an area of concern where improvements are needed."
"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."
"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."
"Scalability depends on the use case. If it is really a big customer with a lot of tests, it might not be a scalable option for them."
"It's a little outdated. It's three years old."
"Bamboo could improve by having compatibility with GitLab. It would be better to have this platform for deploying code and storing container registries. Bamboo does not have a container registry. Additionally, there could be more features added."
AWS CodePipeline is ranked 4th 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 TeamCity, whereas Bamboo is most compared with GitLab, Jenkins, GitHub Actions, Harness and IBM Rational Build Forge. 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.
