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

Tekton vs Travis CI comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Tekton
Ranking in Build Automation
2nd
Average Rating
7.8
Number of Reviews
34
Ranking in other categories
No ranking in other categories
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 November 2024, in the Build Automation category, the mindshare of Tekton is 11.9%, up from 9.9% compared to the previous year. The mindshare of Travis CI is 1.1%, down from 2.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

AjayKrishna - PeerSpot reviewer
If you're dealing with many applications and need a reliable, scalable, and efficient system, I'd recommend this solution
Tekton's most important feature is its cloud-native nature. Unlike Jenkins, which may not scale as efficiently, Tekton's CI pipeline can automatically scale up to handle increased workload demands without needing manual adjustments. Another important aspect is the level of customization offered by Tekton. Each task in the CI pipeline can be customized independently, allowing developers to write code in various languages like shell scripting, Java, or Python and incorporate them into the pipeline as needed. This level of abstraction and customization greatly benefits developers in creating efficient CI pipelines. Also, it can be challenging to understand the logs and troubleshoot issues without clear guidance. It's not always easy to reach technical support and get immediate answers. In my opinion, improvement in this area would be beneficial.
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

"We can make a lot of customizations, and data sharing between tasks using workspaces is very convenient."
"When you run a pipeline, all the jobs are called. It is a very valuable feature that enhances job maintenance overall."
"Tekton is a cloud-native solution. It offers optimal resource consumption, allowing tasks to be run more efficiently and at a lower cost."
"Tekton provides a feature where you can schedule the job."
"It enables enterprises to build a flexible framework atop Tekton, making it easier to define workflows with standard inputs and outputs."
"We just have some configuration files, and it will handle the deployments smoother and faster compared to CI/CD 2.0."
"Tekton is a stable product."
"I find it beneficial to show data from Tekton to another GitHub or Bitbucket pipeline."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"There might be occasional issues with storage or cluster-level logging, which can affect production."
"The user interface of Tekton could be improved."
"Tekton is a good product with all the features I need. There isn't anything that needs improvement."
"The product's version update management process needs improvement."
"For infrastructure deployment, integration is somewhat complex, especially when using Terraform with Tekton. It would be beneficial if this process were simplified."
"Improvement is needed in the documentation and the overall integration process."
"Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers."
"The product's documentation is an area of concern, making it an area where improvements are required."
"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."
"Tekton is an open-source tool."
"The solution is open-source."
"The tool is open-source and free to use."
"It is entirely open source and free of charge."
"The product is free of cost."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
816,562 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
22%
Manufacturing Company
15%
Computer Software Company
12%
Government
8%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
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?
Tekton should have more accessibility for some rare use cases so that we can have more references when applying some techniques to our pipeline.
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

 

Learn More

Video not 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, Jenkins and others in Build Automation. Updated: November 2024.
816,562 professionals have used our research since 2012.