GoCD vs Tekton comparison

"GoCD's open-source nature is valuable."

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

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

"The most valuable features of Tekton include the reusability of tasks, the clean UI interface, and the binding of services and secrets."

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

"The platform's most valuable feature is its wireless capability, which makes installation easy and sets up the flow."

"Tekton has a user interface that facilitates time savings, making it more user-friendly than Jenkins."

"We can make a lot of customizations, and data sharing between tasks using workspaces is very convenient."

"The feature that I like most about Tekton is that it is built for Kubernetes, so we can utilize our resources effectively."

"The tool must be more user-friendly."

"It is difficult to assign different access levels because it relies on separate keys for developer and admin access, which could be simplified."

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

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

"Configuring Tekton requires a deep understanding of Kubernetes, which can be difficult for developers."

"Tekton should include many features to integrate event-driven pipelines."

"One area for improvement is the number of CRDs created during installation. Tekton currently creates 10 to 11 CRDs, which can be overwhelming."

"The product's documentation is an area of concern, making it an area where improvements are required."

"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 UI could be improved, as there are occasional latency issues. The triggering part, especially the CRD installation needs enhancement."

"It tends to occupy a significant amount of disk space on the node, which could potentially pose challenges."

"Improvement is needed in the documentation and the overall integration process."

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

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

"The product is free of cost."

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

"The product is free and open-source."

"Tekton is an open-source tool."

"The solution is open-source."

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