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

Tekton 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

Tekton
Ranking in Build Automation
2nd
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
37
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 October 2025, in the Build Automation category, the mindshare of Tekton is 9.6%, down from 11.8% compared to the previous year. The mindshare of Travis CI is 1.3%, up from 1.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
Tekton9.6%
Travis CI1.3%
Other89.1%
Build Automation
 

Featured Reviews

Prasad Gupta - PeerSpot reviewer
Efficient CI/CD management with significant cost reduction and a user-friendly setup
One area for improvement is the number of CRDs created during installation. Tekton currently creates 10 to 11CRDs, which can be overwhelming. Instead, it would be better to have just one CRD that can handle all the information and create other necessary components automatically. Additionally, more integration capabilities for security, such as DAST, SAST, and IAST, should be directly built into Tekton to facilitate easier implementation of security features.
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 find it beneficial to show data from Tekton to another GitHub or Bitbucket pipeline."
"The tool's most valuable aspect is its compatibility with the cloud-native environment. It can be easily installed on Kubernetes and leverages its resources to run CI/CD pipelines."
"It scales automatically based on the number of tasks or pipelines running, which is efficient and effective for our development needs."
"Tekton is highly customizable, with Kubernetes, we can customize on our own and create custom builders."
"Tekton is a cloud-native solution. It offers optimal resource consumption, allowing tasks to be run more efficiently and at a lower cost."
"The platform's most valuable feature is its wireless capability, which makes installation easy and sets up the flow."
"I like the branching and visualization tools for the pipeline."
"The ability to scale is valuable."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"The tool should improve in terms of output flexibility. It runs on a specific Kubernetes machine, and the persistent memory storage is on a single partition. Improving this aspect could make analyzing logs and toolchain outputs from external tools easier."
"Improvement is needed in the build step."
"If you are a beginner, then accessing the flexibility part can be overwhelming. We think the learning curve of the tool is steep, especially for those who are not already familiar with Kubernetes."
"I didn't get the intention of scalability. Scalability means based on the load, it will automatically gain resources and run. The question of pipeline scalability remains unclear."
"Tekton is a good product with all the features I need. There isn't anything that needs improvement."
"Incorporating AI could be a potential enhancement in the future."
"One area for improvement is the number of CRDs created during installation. Tekton currently creates 10 to 11 CRDs, which can be overwhelming."
"The product's scalability can be challenging when multiple users access it simultaneously."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
 

Pricing and Cost Advice

"The product is free and open-source."
"The solution is open-source."
"Tekton is an open-source tool."
"The product is free of cost."
"The tool is open-source and free to use."
"It is entirely open source and free of charge."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
868,787 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Manufacturing Company
13%
Computer Software Company
10%
Government
8%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise22
No data available
 

Questions from the Community

How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very e...
What do you like most about Tekton?
Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively.
What needs improvement with Tekton?
I didn't get the intention of scalability. Scalability means based on the load, it will automatically gain resources and run. The question of pipeline scalability remains unclear. It's quite easy t...
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

No data available
 

Overview

 

Sample Customers

The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about GitLab, Google, GitHub and others in Build Automation. Updated: September 2025.
868,787 professionals have used our research since 2012.