Bamboo vs Jenkins comparison

"Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process."

"The tool is useful for continuous deployment."

"The most valuable feature of Bamboo is that it is a good tool for CI/CD integration."

"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."

"The platform helps us with automated and timely backup. It provides data replication as well."

"We use Bamboo to automate all our test builds and deployments. It integrates with tools like the ReportPortal to help us check and evaluate processes. When we initiate commands, it automatically checks for scaling issues or failures related to new code. Based on these evaluations, it provides reports in the ReportPortal, helping us decide whether to implement changes."

"One of the big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system."

"It can do the CI pipeline well."

"Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases."

"We used it for all continuous integration parts, like automation testing, deployment, etc."

"The initial setup is simple."

"It can scale easily."

"Very easy to understand for newcomers."

"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."

"Distributed execution of build and test jobs."

"GitHub linking is pretty good. We have a deployment application where we can run our tests and add various variables to be passed as assertions to those tests. This is pretty fluid with Jenkins."

"It's a little outdated. It's three years old."

"The performance around the deployment feature could be improved."

"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."

"It would be great if Bamboo could introduce a more containerized deployment model."

"The tool is not capable of using YAML efficiently."

"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."

"Integrating workflows with other platforms can be challenging. The capabilities of these platforms sometimes fall short compared to others. Initially, it was difficult for us because the plugins were very limited."

"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."

"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."

"The onboarding of Jenkins should be smoother, and it should have more pipelines available as it's deployed on many different servers."

"UI is quite outdated."

"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."

"The solution could improve by having more advanced integrations."

"Jenkins can improve by continuing to add additional plugins for all the new solutions that are coming out within the cloud sphere."

"Creating a new SonarQube project requires a separate job, and we've encountered some integration issues with Docker and the need for better vulnerability checks."

"Developer documentation for plugins, plugin development, integrations: Sometimes it’s tricky to do pretty obvious things."

"The price of Bamboo is reasonable."

"There is a subscription required to use Bamboo."

"The server products for small teams used to offer excellent pricing. However, Atlassian has since changed the offering and the pricing is more expensive. I do still think the solution offers good value for money."

"If Bamboo could provide more flexibility on pricing, that would help. On the agent side, if you want to increase the number of agents it should be less expensive. If they can provide some better pricing model, it will help, whether we are going to use it or are already using it."

"I rate the product’s pricing a five out of ten."

"I rate the solution's pricing a three out of five."

"The pricing for Jenkins is free."

"We are using the free version of Jenkins. There is not a license required to use the solution because it is open-source."

"It is an open source."

"It is a free product."

"There is no cost. It is open source."

"Some of the add-ons are too expensive."

"Jenkins is a free solution, it is open source."

"​It is free.​"