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

GitLab vs Travis CI comparison

 

Comparison Buyer's Guide

Executive Summary

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

GitLab
Ranking in Build Automation
1st
Average Rating
8.6
Reviews Sentiment
7.2
Number of Reviews
82
Ranking in other categories
Application Security Tools (8th), Release Automation (2nd), Static Application Security Testing (SAST) (7th), Rapid Application Development Software (12th), Software Composition Analysis (SCA) (5th), Enterprise Agile Planning Tools (2nd), Fuzz Testing Tools (2nd), DevSecOps (3rd)
Travis CI
Ranking in Build Automation
21st
Average Rating
6.0
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2025, in the Build Automation category, the mindshare of GitLab is 16.9%, down from 18.5% compared to the previous year. The mindshare of Travis CI is 0.6%, down from 2.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Gaurav Chandel - PeerSpot reviewer
Boosted productivity with automated pipelines and seamless collaboration
There are some challenges with repository file management as GitLab may struggle to manage larger files. Improvements could be made regarding size management and file partitioning. Also, the UI has remained the same for a couple of years and could benefit from an update with AI features and better customization.
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

"I have found the most valuable features of GitLab are the GitClone, GitPush, GitPull, GitMatch, GitMit, GitCommit, and GitStatus."
"As a developer, this solution is useful as a repository holder because most of the POC projects that we have are on GitLab."
"GitLab's source control is excellent."
"It scales well."
"For us, Gitlab's most valuable feature is the integration with Cypress. We're using Cypress as an automation tool, so we're using GitLab as a tool for running in parallel."
"The best thing is that as the developers work on separate tasks, all of the code goes there and the other team members don't have to wait on each other to finish."
"The CI/CD pipeline with Helm has significantly improved deployment speed and efficiency."
"CI/CD and GitLab scanning are the most valuable features."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"We would like to generate document pages from the sources."
"There is a need to improve or adopt AI into the ecosystem like a co-pilot, which Microsoft has done with GitHub."
"This solution could be improved by adding modifications such as slack notifications."
"The solution could be faster."
"It has fewer options, and its UI is not so user-friendly."
"I have encountered issues with the deployment of CI/CD pipelines, especially dealing with variable environments."
"Some of the scripts that we encountered in GitLab were not fully functional and threw up errors."
"I don't really like the new Kubernetes integration because it is pretty focused on the on-premise environment, but we're in a hybrid environment."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
 

Pricing and Cost Advice

"It seems reasonable. Our IT team manages the licenses."
"I think that we pay approximately $100 USD per month."
"We are using the open-source version."
"My company uses the free version of GitLab, which is GitLab Community Edition. There is a licensed version also available for GitLab."
"GitLab is a free solution to use."
"GitLab is an open-source solution."
"The solution is based on a licensing model that includes technical support and is paid annually."
"GitLab is highly priced for smaller teams, but it's okay if considering a user base of thousands."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
839,422 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
28%
Financial Services Firm
11%
Computer Software Company
11%
Manufacturing Company
8%
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 GitLab?
I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently.
What is your experience regarding pricing and costs for GitLab?
The pricing of GitLab is reasonable, aligning with what I consider to be average compared to competitors.
What needs improvement with GitLab?
Certain features in Jira are not available in GitLab, such as the functionality to have weights at the milestone and epic levels. Hopefully, these features will be resolved with work items in GitLa...
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

Fuzzit
No data available
 

Overview

 

Sample Customers

1. NASA  2. IBM  3. Sony  4. Alibaba  5. CERN  6. Siemens  7. Volkswagen  8. ING  9. Ticketmaster  10. SpaceX  11. Adobe  12. Intuit  13. Autodesk  14. Rakuten  15. Unity Technologies  16. Pandora  17. Electronic Arts  18. Nordstrom  19. Verizon  20. Comcast  21. Philips  22. Deutsche Telekom  23. Orange  24. Fujitsu  25. Ericsson  26. Nokia  27. General Electric  28. Cisco  29. Accenture  30. Deloitte  31. PwC  32. KPMG
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.
839,422 professionals have used our research since 2012.