We performed a comparison between Bamboo and CircleCI 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."Bamboo was used extensively in our organization for PCA compliance."
"One of the big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system."
"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."
"The most valuable feature of Bamboo is that it is a good tool for CI/CD integration."
"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 most valuable features are compiling and deployment."
"Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process."
"It's a stable product."
"The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"The solution offers continuous integration and continuous delivery."
"The ability to automate the build process in a seamless way and run workflows effortlessly. It supports parallel builds so it can scale well. Also, it covers the basics of any build and integration tool, including email notifications (especially when tests are fixed), project insights, etc."
"Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts."
"Enables us to detect exactly which build failed and why, and to push multiple builds to our production environment at a very fast rate."
"It's a little outdated. It's three years old."
"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."
"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 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 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."
"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."
"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."
"Integration with Microsoft Azure is one area for improvement. Azure is growing in its user base, and supports various cloud infrastructure components such as Service Fabric, App Service, etc. Some of Azure’s deployment models (like Kudu) require a steep learning curve, but if CircleCI would come up with such features (deployment to App Service) out of the box, it would be amazing."
"There needs to be some improvement in the user interface of CircleCI."
"Billing is a mess."
"The solution’s pricing could be better."
Bamboo is ranked 5th in Build Automation with 20 reviews while CircleCI is ranked 11th in Build Automation with 5 reviews. Bamboo is rated 7.4, while CircleCI is rated 6.6. The top reviewer of Bamboo writes "High availability, helpful support, and plenty of plugins available". On the other hand, the top reviewer of CircleCI writes "Unhelpful support, unclear billing, and has offers ability to track usage". Bamboo is most compared with GitLab, Jenkins, GitHub Actions, Harness and Tekton, whereas CircleCI is most compared with TeamCity, Tekton, GitHub Actions, Jenkins and AWS CodeBuild. See our Bamboo vs. CircleCI 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.