We compared GitLab and Tekton based on our user's reviews in several parameters.
Users find GitLab to offer competitive pricing, flexible licensing options, and positive ROI, with room for improvement in user interface, speed, and performance. They appreciate robust version control features and strong customer support. On the other hand, Tekton is praised for its ease of use, reliable customer service, and seamless integration, with users highlighting the customizable features and positive impact on productivity and efficiency. Both tools have varying feedback on the time required for deployment and setup, showing differences in user experiences.
Features: GitLab stands out with its robust version control capabilities, comprehensive issue tracking system, and seamless collaboration tools. On the other hand, Tekton excels in its ease of use, extensive customization options, and great reliability.
Pricing and ROI: In terms of setup cost, users find both GitLab and Tekton to be easy and straightforward. GitLab offers flexible licensing options for individuals and businesses, while Tekton users have not expressed any difficulties or dissatisfaction with licensing., The ROI for GitLab has been positively rewarding, providing users with valuable investment for their projects. Tekton has also shown positive ROI, improving productivity, efficiency, accuracy, cost savings, and customer satisfaction. Users appreciate its versatility and ease of use.
Room for Improvement: Some areas for improvement in the GitLab product include its user interface and navigation, performance and speed for larger projects, project management features, and the code review process. Meanwhile, users of Tekton expressed the need for improvements in certain aspects of the product.
Deployment and customer support: The user reviews for GitLab and Tekton differ in terms of how they define and separate the deployment and setup phases. Some users see them as separate phases, while others consider them as the same period., In terms of customer service and support, GitLab's product is highly praised for its prompt assistance, effective troubleshooting, and helpful guidance. They are known for going above and beyond to resolve issues and have a strong community. On the other hand, Tekton's customer service is also highly praised for its promptness, helpfulness, reliability, and efficiency. Both products ensure a positive experience for customers.
The summary above is based on 53 interviews we conducted recently with GitLab and Tekton users. To access the review's full transcripts, download our report.
"The solution's most valuable feature is that it is compatible with GitHub. The product's integration capabilities are sufficient for our small company of 35 people."
"The scalability is good."
"Everything is easy to configure and easy to work with."
"It's a great toolbox where the CI/CD pipeline is the fundamental component, but there are so many other features that you can pull from, which makes it a very powerful tool. My current client is using AWS, and they can, of course, use AWS CodePipeline, but GitLab is much more mature than that, and it also gives you the freedom to decide to go to another platform or have a multi-cloud strategy and things like that. That freedom for me is also very valuable."
"The solution has an established roadmap that lays out its plans for upgrades over the next two to three years."
"The code merging capability is something that we use very frequently."
"The merging feature makes it easy later on for the deployment."
"I like that it's easy to deploy our services over GitLab. The customer support is also good with a really active community. You have a lot of support that you can get online with your stack. That is probably one of the benefits of using GitLab. It's also really fast."
"Tekton is an orchestrator. It provides seamless integration for our pipelines. It offers robust support for executing tasks within the pipeline, allowing us to set up and run pipelines quickly."
"Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively."
"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."
"There was a problem with the build environment when we were looking at developing iOS applications. iOS build require Mac machines and there are no Mac machines provided by GitLab in their cloud. So to build for mobile iOS application, we needed to use our own Mac machine within our own infrastructure. If GitLab were to provide a feature such that an iOS application could also be built through GitLab directly, that would be great."
"The pricing model of GitLab is an issue for me."
"GitLab could improve by having more plugins and better user-friendliness."
"This solution could be improved by adding modifications such as slack notifications."
"We do face issues in our company when we run out of disk space."
"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."
"I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors."
"It's more related to the supporting layer of features, such as issue management and issue tracking. We tend to always use, for example, Jira next to it. That doesn't mean that GitLab should build something similar to Jira because that will always have its place, but they could grow a bit in those kinds of supporting features. I see some, for example, covering ITSM on a DevOps team level, and that's one of the things that I and my current client would find really helpful. It's understandably not going to be their main focus and their core, and whenever you are with a company that needs a bit more advanced features on that specific topic, you're probably still going to integrate with another tool like Jira Service Management, for example. However, some basic features on things like that could be really helpful."
"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."
"Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers."
"There might be occasional issues with storage or cluster-level logging, which can affect production."
GitLab is ranked 1st in Build Automation with 70 reviews while Tekton is ranked 4th in Build Automation with 3 reviews. GitLab is rated 8.6, while Tekton is rated 6.4. The top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". On the other hand, the top reviewer of Tekton writes "Provides seamless integration for pipelines, allowing easy setup and execution of tasks but working with YAML files in Tekton can be challenging to modify ". GitLab is most compared with Microsoft Azure DevOps, Bamboo, SonarQube, AWS CodePipeline and TeamCity, whereas Tekton is most compared with GitHub Actions, Harness, Travis CI, Jenkins and CircleCI. See our GitLab vs. Tekton report.
See our list of best Build Automation vendors.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
