We performed a comparison between Bamboo, CircleCI, and Jenkins based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation."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 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."
"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."
"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 platform helps us with automated and timely backup. It provides data replication as well."
"The most valuable features are compiling and deployment."
"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 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."
"The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"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."
"The solution offers continuous integration and continuous delivery."
"It's a stable product."
"It has a lot of community posts and support."
"The most valuable feature is its ability to connect with different tools and technologies."
"It is very useful for us to be able to collect and manage automatic processing pipelines."
"This solution has helped us in automating the build and test process, reducing time."
"It is open source, flexible, scalable, and easy to use. It is easy to maintain for the administrator. It is a continuous integration tool, and its enterprise version is quite mature. It has good integrations and plug-ins. Azure DevOps can also be integrated with Jenkins."
"The initial setup is pretty simple."
"Has enabled full automation of the company."
"The most valuable feature of the solution is its integration between different tools."
"It's a little outdated. It's three years old."
"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."
"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."
"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."
"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."
"The marketing strategy of Bamboo is an area of concern where improvements are needed."
"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."
"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."
"Billing is a mess."
"There needs to be some improvement in the user interface of CircleCI."
"The solution’s pricing could be better."
"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."
"It does not have a very user-friendly interface."
"Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly."
"Jenkins can be improved, but it's difficult for me to explain. The initial setup could be more straightforward. If you connect Jenkins with bookings and lockouts, it can be challenging."
"Improvement-wise, I would want the solution's user interface to be changed for the better. In short, the solution can be made more user-friendly."
"There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python. We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided."
"The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift."
"The enterprise version is less stable than the open-source version."
"Jenkins needs a faster deployment process."
