Jenkins vs Tekton comparison

"I like the business logs. It's a very useful tool. Client-server communication is also very fast."

"It's a powerful tool for CI/CD."

"The most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."

"The most valuable feature of Jenkins is its open source."

"Jenkins is particularly valuable since it saves time by automating manual tasks."

"Jenkins has been instrumental in automating our build and deployment processes."

"It is a stable solution."

"For business needs, Jenkins is the most relevant choice because it can be self-hosted, the price is good, it’s robust, and requires almost no effort for maintenance."

"Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively."

"The tool offers flexibility and compatibility."

"I like the setup of the dashboard."

"When you run a pipeline, all the jobs are called. It is a very valuable feature that enhances job maintenance overall."

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

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

"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 platform's most valuable feature is its wireless capability, which makes installation easy and sets up the flow."

"There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python. We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided."

"We sometimes face challenges during version upgrades, such as failures when migrating Kubernetes versions."

"It does not have a very user-friendly interface."

"We would like to see the addition of mobile simulators support to this solution, as part of its open-source offering. We currently have to carry out manual testing for these platforms."

"I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."

"UI is quite outdated."

"The upgrades need improvement."

"A more user-friendly UI for creating pipelines would be helpful."

"The stability issues can be there."

"Incorporating AI could be a potential enhancement in the future."

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

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

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

"While Tekton is highly effective for Kubernetes-based setups, it might not suit users who require more control over bare-metal environments."

"If you are a beginner, then accessing the flexibility part can be overwhelming. We think the learning curve of the tool is steep, especially for those who are not already familiar with Kubernetes."

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

"I used the free OSS version all the time. It was enough for all my needs."

"Some of the add-ons are too expensive."

"Jenkins is open source."

"The tool is open-source."

"The pricing for Jenkins is free."

"Jenkins is open-source, so it is free."

"We are using the freeware version of Jenkins."

"This is an open-source solution for the basic features. However, if an organization wishes to include specific functionality, outside of the basic package, there are extra costs involved."

"The product is free and open-source."

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

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

"The product is free of cost."

"The solution is open-source."

"Tekton is an open-source tool."