CloudBees vs Tekton comparison

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

"The most beneficial aspect is that CloudBees integrates with everything, like version one, GitHub, and PDM."

"The security audit product offered by CloudBees is particularly beneficial in automating audit processes, which reduces the time developers spend on audits."

"CloudBees is a user-friendly tool."

"One recent product feature that stands out is the pipeline explorer, which is providing significant value for us right now."

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

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

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

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

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

"Tekton allows you to categorize tasks according to your needs and minimizes the amount of code needed."

"The installation process is seamless, requiring fewer resources compared to Jenkins."

"The platform's most valuable feature is its cloud-native and Kubernetes-ready design."

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

"It enables enterprises to build a flexible framework atop Tekton, making it easier to define workflows with standard inputs and outputs."

"The product's best feature is its ease of implementation."

"I think a preview of the errors would be good just at the point where the error occurs."

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

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

"It could improve the document upload process."

"To use the tool, you need to be familiar with the tool itself and with how it will be incorporated into the culture."

"The setup is somewhat complicated. You need a cloud architect and engineer to set it up properly. The initial setup will take time, so you need a good engineer and architect to handle it."

"A lot of stability issues are there with CloudBees."

"The platform could integrate better with other tools and support external tools directly."

"The product's version update management process needs improvement."

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

"Initially, working with YAML configuration can be challenging using the solution."

"Tekton could improve by adding better documentation."

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

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

"Tekton is a good product with all the features I need. There isn't anything that needs improvement."

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

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

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

"Tekton is an open-source tool."

"The product is free of cost."

"The product is free and open-source."

"The solution is open-source."