GoCD vs Tekton comparison

"The most notable aspect is its user interface, which we find to be user-friendly and straightforward for deploying and comprehending pipelines. We have the ability to create multiple pipelines, and in addition to that, the resource consumption is impressive."

"Permission separations mean that we can grant limited permissions for each team or team member."

"The UI is colorful."

"The tool's most valuable aspect is its compatibility with the cloud-native environment. It can be easily installed on Kubernetes and leverages its resources to run CI/CD pipelines."

"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."

"The flexibility of Tekton is the most valuable feature"

"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."

"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."

"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."

"The aspect that requires attention is the user management component. When integrating with BitLabs and authenticating through GitLab, there are specific features we desire. One important feature is the ability to import users directly from GitLab, along with their respective designations, and assign appropriate privileges based on that information. Allocating different privileges to users is a time-consuming process for us."

"The documentation really should be improved by including real examples and more setup cases."

"The tool must be more user-friendly."

"Some of the tool's cons include its minimalistic dashboard, which lacks detailed information and control compared to other tools like Jenkins or GitLab. Additionally, it's primarily used by Japanese companies."

"There might be occasional issues with storage or cluster-level logging, which can affect production."

"I'm a bit worried about scaling Tekton from the point of view of big CI/CD processes."

"Tekton lacks sufficient documentation"

"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."

"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."

"This is an open-source solution and it is inexpensive."

"It's an open-source and free tool."

"It is entirely open source and free of charge."

"The tool is open-source and free to use."