Try our new research platform with insights from 80,000+ expert users

Bamboo vs Travis CI comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Bamboo
Ranking in Build Automation
6th
Average Rating
7.4
Reviews Sentiment
6.8
Number of Reviews
22
Ranking in other categories
No ranking in other categories
Travis CI
Ranking in Build Automation
21st
Average Rating
6.0
Reviews Sentiment
3.1
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Build Automation category, the mindshare of Bamboo is 7.4%, down from 9.1% compared to the previous year. The mindshare of Travis CI is 0.7%, down from 1.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Andrea Carella - PeerSpot reviewer
High availability, helpful support, and plenty of plugins available
I have used Google Cloud Platform and Amazon AWS for implementing Bamboo. It is not difficult to complete. The length of time it takes for deployment depends on a lot of variables, such as how the pipeline is deployed and what type of infrastructure is present. However, it typically takes only hours not days. I rate the setup of Bamboo a nine out of ten.
Pravar Agrawal - PeerSpot reviewer
YAML-based configuration and simple deployment but user interface needs modernizing
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user-friendly; it feels like it was stuck in 2010. It is very basic and designed for lightweight CI work, and it cannot handle heavy CI. You cannot do branched flows, and you will have to write shell scripts to send calls here and there. The pipelines are not as detailed as some other CI/CD tools. If Travis is down, you don't have any control over it and need to reach out to their customer support.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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 features are compiling and deployment."
"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."
"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 tool is useful for continuous deployment."
"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 only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"It would be great if Bamboo could introduce a more containerized deployment model."
"The marketing strategy of Bamboo is an area of concern where improvements are needed."
"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."
"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."
"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’s technical support services, in terms of speed of response, need improvement."
"It's a little outdated. It's three years old."
"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."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
 

Pricing and Cost Advice

"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."
"The price of Bamboo is reasonable."
"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."
"There is a subscription required to use Bamboo."
"I rate the solution's pricing a three out of five."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Comparison Review

it_user217035 - PeerSpot reviewer
May 27, 2015
Bamboo vs. Jenkins
A biased and subjective comparison of Bamboo and Jenkins as CI servers for mobile development, based on practical experience with both. Continuous Integration and Continuous Deployment (Delivery, Distribution) has been around for quite a while. But surprisingly enough on a global scale it pretty…
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Manufacturing Company
14%
Computer Software Company
12%
Government
12%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Bamboo?
Bamboo's integration with the rest of Atlassian's tech tools, like Jira, helps manage the end-to-end development and release process.
What needs improvement with Bamboo?
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 we...
What is your experience regarding pricing and costs for Travis CI?
I'm not too sure about the pricing of Travis or how the agreement works.
What needs improvement with Travis CI?
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user...
What is your primary use case for Travis CI?
Travis CI is mainly used to run integration tests as part of the deployment, which I do on Kubernetes. The Travis workflows are integrated with any changes in my code. It will have different jobs, ...
 

Comparisons

 

Overview

 

Sample Customers

Neocleus, MuleSoft, Interspire
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about GitLab, Google, Jenkins and others in Build Automation. Updated: March 2025.
845,406 professionals have used our research since 2012.