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

GitHub Actions vs Tekton comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

GitHub Actions
Ranking in Build Automation
5th
Average Rating
8.4
Number of Reviews
19
Ranking in other categories
No ranking in other categories
Tekton
Ranking in Build Automation
2nd
Average Rating
7.6
Number of Reviews
36
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of December 2024, in the Build Automation category, the mindshare of GitHub Actions is 10.4%, up from 1.8% compared to the previous year. The mindshare of Tekton is 12.0%, up from 9.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

MohamedMostafa1 - PeerSpot reviewer
Handles scalability well, automatically managing execution infrastructure without requiring additional configurationsThe automation feature of GitHub Actions is
I find the automation feature of GitHub Actions most valuable for our building processes. It integrates seamlessly with GitHub, so there's no extra configuration needed, making the building process easy and efficient. GitHub Actions handles scalability well, automatically managing execution infrastructure without requiring additional configurations. We haven't yet explored GitHub Actions' support for AI projects, as we haven't used its AI capabilities.
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.

Quotes from Members

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

Pros

"I find the automation feature of GitHub Actions most valuable for our building processes. It integrates seamlessly with GitHub, so there's no extra configuration needed, making the building process easy and efficient. GitHub Actions handles scalability well, automatically managing execution infrastructure without requiring additional configurations. We haven't yet explored GitHub Actions' support for AI projects, as we haven't used its AI capabilities."
"The most valuable feature of the solution is that it is a good product that offers stability and performance."
"The most valuable features of GitHub Actions include its seamless integration within GitHub, which simplifies the CI/CD pipeline setup. The scalability of using different types of runners—both public and private runners—enhances deployment flexibility."
"GitHub Actions can be easily configured, especially for environment variables and secrets. The UI is understandable and user-friendly for setting up CI/CD pipelines. I prefer tools like GitLab, where the pipeline starts quickly and is accessible near the commits for easy access. However, many CI/CD tools are interchangeable due to similar features of GitHub Actions and other similar tools."
"I have optimized job execution time by running test scripts in parallel and creating multiple pipelines; we've significantly reduced execution times. What could take 50 minutes can be cut down to just 8 to 10 minutes through these optimizations."
"The product's most beneficial feature is the ability to create workflows within the solution."
"The main benefit is collaboration. It allows us to easily collaborate with other developers, regardless of location. For example, we can collaborate with both our African and German colleagues seamlessly. It's platform-agnostic, so it is flexible and not tied to any OS, so we can work on Linux, Windows, web, and even Oracle applications. It's flexible, reliable, and overall an excellent tool for our needs."
"It offers numerous built-in features for pipeline management, release management, and even work item tracking on boards, which makes it a versatile tool that seamlessly integrates with hardware and facilitates optimization."
"Tekton is a stable product."
"The most valuable features of Tekton include the reusability of tasks, the clean UI interface, and the binding of services and secrets."
"I would say the customization ability that Tekton provides is good."
"When you run a pipeline, all the jobs are called. It is a very valuable feature that enhances job maintenance overall."
"You can isolate most Tekton assets in the Kubernetes namespace for your feature branch. This allows you to freely change Tekton assets and objects to adapt to your feature branch and requirements."
"It enables enterprises to build a flexible framework atop Tekton, making it easier to define workflows with standard inputs and outputs."
"I like the branching and visualization tools for the pipeline."
"Tekton is serverless and runs on OpenShift, and we leverage Tekton to take full advantage of the Kubernetes features such as running and scaling the solution in PaaS."
 

Cons

"Sometimes incremental steps should be taken during deployment instead of trying to execute all tasks simultaneously, particularly when dealing with AWS EKS clusters and Helm charts."
"The only issue I have faced is with authorization, particularly when configuring the GitHub token correctly."
"The main challenge I've experienced is with integration, particularly uploading to OneDrive, which was more complex compared to Google Drive or AWS S3 bucket."
"The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly."
"The minor drawback of GitHub Actions is the management of the dashboard and pipeline runs, which needs improvement. The dashboard for running pipelines could be better."
"The primary area for improvement I see is in artifact management, especially for saving screenshots or videos from failed tests or data-driven actions. Currently, the configuration for saving these artifacts is complex."
"My company would want to see some AI features in the tool as it can add value to the product."
"The UI could be better."
"Improvement is needed in the build step."
"Compared to traditional tools like Jenkins, Tekton lacks a lot of features. It's not efficient in managing conflicts between multiple pipelines."
"Improvements could include introducing a UI-based pipeline development feature, such as drag and drop, which would help individuals with limited technical knowledge start building pipelines."
"When we started with Tekton around 2021 or early 2022, the community support was somewhat limited, which posed challenges when dealing with issues or debugging. We had to rely on Red Hat OpenShift support to overcome these challenges. However, I believe that these issues will naturally improve over timeas the developer community grows stronger. From a technical perspective, I haven't had the opportunity to deeply evaluate the product end-to-end, especially in the past year or so, when I've been less involved with it."
"While Tekton is highly effective for Kubernetes-based setups, it might not suit users who require more control over bare-metal environments."
"Initially, working with YAML configuration can be challenging using the solution."
"The stability issues can be there."
"It would be beneficial to find case studies or more information on complex implementations."
 

Pricing and Cost Advice

"The product is slightly more expensive than some alternatives."
"It is free and open platform, so I would rate it 1 out of 10."
"The tool's price is okay and reasonable."
"It's low-priced. Not high, but definitely low."
"Regarding cost, as an enterprise, we negotiate our license and expenses, so I can't provide a specific rating for that."
"The cost for GitHub Actions may be around $45 dollars per user."
"For our basic usage, we didn't have to pay."
"Price-wise, GitHub Actions is okay. If I want to use the product's advanced features, then I need to pay the licensing charges for the solution."
"The product is free and open-source."
"It is entirely open source and free of charge."
"The solution is open-source."
"The product is free of cost."
"Tekton is an open-source tool."
"The tool is open-source and free to use."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
823,875 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
13%
Manufacturing Company
11%
Healthcare Company
6%
Financial Services Firm
22%
Manufacturing Company
15%
Computer Software Company
13%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about GitHub Actions?
I have optimized job execution time by running test scripts in parallel and creating multiple pipelines; we've significantly reduced execution times. What could take 50 minutes can be cut down to j...
What is your experience regarding pricing and costs for GitHub Actions?
There are pricing considerations where exceeding the free hours given in a month incurs additional costs. GitHub provides a free version with certain hours, which seems reasonable for my usage.
What needs improvement with GitHub Actions?
The main challenge I've experienced is with integration, particularly uploading to OneDrive, which was more complex compared to Google Drive or AWS S3 bucket. I had to conduct extensive research to...
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?
Regarding areas for improvement in Tekton, I have not encountered significant issues. It works well for our use case. However, incorporating AI could be a potential enhancement in the future.
 

Comparisons

 

Learn More

 

Overview

 

Sample Customers

Information Not Available
The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture
Find out what your peers are saying about GitHub Actions vs. Tekton and other solutions. Updated: December 2024.
823,875 professionals have used our research since 2012.