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.
"This is a scalable solution. We had around 200 users working with it."
"We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people."
"GitLab's best features are continuous integration and fast deployment."
"I like that you can use GitLab as a double-sided solution for both DevOps and version management. It's a good product for working in these two areas, and the user interface makes it easy to understand."
"GitLab is very useful for pipelines, continuous integration, and continuous deployment. It is also stable."
"The tool helps to integrate CI/CD pipeline deployments. It is very easy to learn. Its security model is good."
"I have had no problem with the stability of the solution."
"The user interface is really good so that helps with huge teams who need to collaborate."
"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 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."
"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."
"I would like to see better integration with project management tools such as Jira."
"Expand features to match other tools such as a static code analysis tool so third-party integrations are not required."
"The solution does not have many built-in functions or variables so scripting is required."
"We would like to have easier tutorials. Their tutorials are too technical for a user to understand. They should be more detailed but less technical."
"GitLab's Windows version is yet not available and having this would be an improvement."
"We'd like to see better integration with the Atlassian ecosystem."
"Their RBAC is role-based access, which is fine but not very good."
"It is a little complex to set up the pipelines within the solution."
"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."
"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."
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, Travis CI, Harness, 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.