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

AWS CodeBuild vs Tekton 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

AWS CodeBuild
Ranking in Build Automation
11th
Average Rating
8.2
Reviews Sentiment
7.7
Number of Reviews
10
Ranking in other categories
No ranking in other categories
Tekton
Ranking in Build Automation
2nd
Average Rating
7.6
Reviews Sentiment
7.2
Number of Reviews
36
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Build Automation category, the mindshare of AWS CodeBuild is 1.2%, down from 1.5% compared to the previous year. The mindshare of Tekton is 12.3%, up from 10.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

Udhay Prakash Pethakamsetty - PeerSpot reviewer
Provides good integrations, is flexible, and has a comparable price
The product must provide more integrations. It is a replica of Jenkins. We have a management overhead. When I build artifacts stored outside the S3 bucket, it will have additional charges on the storage volumes. If we use S3 buckets regularly, it is fine. However, when we store somewhere else, it will be an issue. There is no persistent storage or preservation of workspace between the builds. We must fix the dependencies every time, even if the dependencies are the same. It is unnecessary.
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

"The initial setup of CodeBuild is easy."
"The integration is a good feature."
"The tool is used to build and test code. I find its biggest advantages are elasticity and reliability. We can easily assign as many computing resources as needed to build our code, which is much simpler than traditional methods that require server upgrades. It's a serverless tool, so it's very flexible and elastic."
"A valuable feature is the support for third-party repositories such as Bitbucket, GitLab, or GitHub."
"It works seamlessly with AWS Elastic Container Registry (ECR)."
"The integration is a good feature."
"One of the main features I value in CodeBuild compared to previous experiences, like using Jenkins, is its ability to handle tasks automatically with AWS, requiring only proper setup of the check file."
"CodeBuild supports various platforms and coding."
"Tekton's inclusion in Kubernetes deployment offers better visibility on how Tekton is performing within a cluster. It is lightweight and not as heavy as Jenkins to maintain."
"I find it beneficial to show data from Tekton to another GitHub or Bitbucket pipeline."
"The platform's most valuable feature is its cloud-native and Kubernetes-ready design."
"I like the branching and visualization tools for the pipeline."
"Tekton allows you to categorize tasks according to your needs and minimizes the amount of code needed."
"The product's best feature is its ease of implementation."
"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."
"One of the best things I appreciate is that Tekton runs on the Kubernetes platform. This is very useful when working on a project with other team members. For instance, suppose we have a very big project that requires building a large amount of source code or running many unit tests. During the build and unit test phases, Tekton on Kubernetes allows us to have a scalable machine to handle these tasks. This scalability is the most useful aspect for me."
 

Cons

"While working on building images for multiple applications within a single script, I encountered an issue where looping functionality was not supported as expected."
"They can further improve the integration of the Bitbucket for CodeBuild."
"For improvement, I'd suggest more build instance-type options. There's a big jump from 15 gigabytes of RAM to 150, and I'd like something in between as the larger option is too expensive for our needs."
"Notifications could be added, or SNS integration could be included so that notifications can be received on every build, whether the build fails or succeeds."
"There is no persistent storage or preservation of workspace between the builds."
"The front-end interface and the management are somewhat challenging, and there's a lot of space for improvement."
"One of the main challenges is that if the environment is not set up properly, it will result in issues such as image errors."
"The deployment fails sometimes."
"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."
"The product's documentation is an area of concern, making it an area where improvements are required."
"Improvement is needed in the documentation and the overall integration process."
"The stability issues can be there."
"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."
"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."
"It would be better if Tekton could show the YAML file while it is running, similar to GitHub pipelines, to provide more visibility on what's happening."
"Incorporating AI could be a potential enhancement in the future."
 

Pricing and Cost Advice

"AWS CodeBuild is free. We only pay for our code's compute resources during the build process. For example, if our code takes ten minutes to build, we only pay for those ten minutes of computing time. CodeDeploy and CodePipeline are free because they're serverless and don't require computing resources. CodeCommit has minimal costs for storing code."
"Despite the cost, it is worth the investment."
"We pay a monthly licensing fee."
"The product is free and open-source."
"The solution is open-source."
"The product is free of cost."
"The tool is open-source and free to use."
"Tekton is an open-source tool."
"It is entirely open source and free of charge."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
13%
Manufacturing Company
12%
Media Company
9%
Financial Services Firm
24%
Manufacturing Company
13%
Computer Software Company
12%
Government
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about AWS CodeBuild?
It works seamlessly with AWS Elastic Container Registry (ECR).
What is your experience regarding pricing and costs for AWS CodeBuild?
Regarding pricing, AWS services are quite expensive compared to open source tools like Git that are available for free.
What needs improvement with AWS CodeBuild?
We had integration issues with a tool called Octopus Deploy while using CodeBuild. AWS support helped us resolve it, however, it could be better.
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

 

Also Known As

CodeBuild
No data available
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture
Find out what your peers are saying about AWS CodeBuild vs. Tekton and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.