Bamboo vs Jenkins comparison

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

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

"In my experience Bamboo is scalable."

"The most valuable features are compiling and deployment."

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

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

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

"I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company."

"Jenkins is a very mature product."

"I like the business logs. It's a very useful tool. Client-server communication is also very fast."

"Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead."

"Jenkins's open-based framework is very valuable."

"A lot of support material exists via a single web search of exactly what you're looking for."

"The most valuable features of Jenkins are the integration with GitHub, and the automation for deployment."

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

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

"Bamboo’s technical support services, in terms of speed of response, need improvement."

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

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

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

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

"They need to improve their documentation."

"Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable."

"Jenkins needs a faster deployment process."

"The disadvantage of Jenkins is writing Groovy scripts. There are other CI tools where you do not need to write this many scripts to manage and deploy."

"Jenkins could improve the integration with other platforms."

"There are some issues with Jenkins, especially with the SIP job."

"Adding support for OIDC and internal user databases simultaneously would improve Jenkins."

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

"There is a subscription required to use Bamboo."

"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 solution's pricing a three out of five."

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

"The price of Bamboo is reasonable."

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

"Jenkins is open-source, so it is free."

"​It is free.​"

"Jenkins is an open-source platform."

"Jenkins is not expensive and reasonably priced."

"We are using the free version of Jenkins. There are no costs or licensing."

"The pricing for Jenkins is free."

"It is a cheap solution."

"We are using the freeware version of Jenkins."