CloudBees vs Tekton comparison

"CloudBees is the Jenkins tool for building and deploying. There's open-source Jenkins, which is free and can be used by any organization, but it offers a different architecture for Jenkins. If your organization is larger, you might choose the architecture. This way, you can have different masters for different applications, and different teams can manage their masters separately. However, a single person can still control all the masters, whoever manages it for the organization."

"The solution's most valuable feature is its flexibility."

"CloudBees assists by automating tasks, previously done manually, in the pipeline setup."

"Scalability largely depends on how the tool is set up within your infrastructure"

"CloudBees's user interface is very simple and user-friendly."

"I find the automation feature most valuable. CloudBees is highly scalable and supports both small and large teams. The deployment process is also faster when compared to on-premise."

"It’s a very good tool for auditing your project pipelines as well."

"The most valuable feature of the solution is that its GUI is quite simple."

"I would say the customization ability that Tekton provides is good."

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

"I like the branching and visualization tools for the pipeline."

"The 'promote' feature is beneficial as it simplifies deployment processes by allowing easy promotion of applications to different environments without needing to re-run CI/CD processes."

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

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

"We just have some configuration files, and it will handle the deployments smoother and faster compared to CI/CD 2.0."

"Tekton provides a feature where you can schedule the job."

"There are connection issues with CloudBees, specifically between Sybase and CloudBees. W"

"The user interface of CloudBees is good but could be even more intuitive. Improving the user-friendliness of the interface and having simpler setup configurations would greatly benefit new users."

"If you're logged in and working for about thirty minutes and then go idle for five to ten minutes, Jenkins will prompt you to re-authenticate."

"We did face some challenges, particularly with the infrastructure."

"Sometimes, there are performance issues, however, they may be due to our organization's configuration."

"To improve efficiency, they should focus on smoother label deployment."

"The problem with CloudBees is that when you merge it, the pipelines would randomly fail multiple times."

"There could be improvements in the ease of use."

"RBAC is really needed for Tekton."

"It would be beneficial to find case studies or more information on complex implementations."

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

"Compared to traditional tools like Jenkins, Tekton lacks a lot of features. It's not efficient in managing conflicts between multiple pipelines."

"Tekton could improve by adding better documentation."

"For infrastructure deployment, integration is somewhat complex, especially when using Terraform with Tekton. It would be beneficial if this process were simplified."

"One area where Tekton can improve is log management."

"The product's scalability can be challenging when multiple users access it simultaneously."

"The solution is open-source."

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

"The product is free of cost."

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

"The product is free and open-source."

"Tekton is an open-source tool."