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

GoCD 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

GoCD
Ranking in Build Automation
16th
Average Rating
7.6
Reviews Sentiment
7.1
Number of Reviews
7
Ranking in other categories
Application Lifecycle Management (ALM) Suites (14th), Release Automation (10th)
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 July 2025, in the Build Automation category, the mindshare of GoCD is 1.5%, down from 1.6% compared to the previous year. The mindshare of Travis CI is 0.9%, down from 1.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Nishant Narayan Singh - PeerSpot reviewer
Simplifies the pipeline process, but the access control system needs enhancement
One area of product improvement is the access control system. It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be simplified. The folder structure is another aspect that could be enhanced, as all jobs are displayed on a single page without the clear organization seen in Jenkins. Implementing a more structured approach to organizing jobs would improve user experience. AI could simplify job creation. For example, instead of manually editing pipelines as code, an AI tool could allow users to input variables and automatically generate the required jobs. It would help reduce human errors, such as issues that arise from incorrect edits in large code files.
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

"The UI is colorful."
"Permission separations mean that we can grant limited permissions for each team or team member."
"GoCD's open-source nature is valuable."
"The most notable aspect is its user interface, which we find to be user-friendly and straightforward for deploying and comprehending pipelines. We have the ability to create multiple pipelines, and in addition to that, the resource consumption is impressive."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"The tool must be more user-friendly."
"It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be simplified."
"The documentation really should be improved by including real examples and more setup cases."
"The aspect that requires attention is the user management component. When integrating with BitLabs and authenticating through GitLab, there are specific features we desire. One important feature is the ability to import users directly from GitLab, along with their respective designations, and assign appropriate privileges based on that information. Allocating different privileges to users is a time-consuming process for us."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
 

Pricing and Cost Advice

"This is an open-source solution and it is inexpensive."
"It's an open-source and free tool."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
863,564 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Retailer
9%
Recreational Facilities/Services Company
8%
Government
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What needs improvement with GoCD?
One area of product improvement is the access control system. It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be sim...
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

 

Also Known As

Adaptive ALM, Thoughtworks Go
No data available
 

Overview

 

Sample Customers

Ancestry.com, Barclay Card, AutoTrader, BT Financial Group, Gamesys, Nike, Vodafone, Haufe Lexware, Medidata, Hoovers
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about GitLab, Google, Jenkins and others in Build Automation. Updated: July 2025.
863,564 professionals have used our research since 2012.