Bamboo vs Tekton comparison

"It can do the CI pipeline well."

"Bamboo was used extensively in our organization for PCA compliance."

"In my experience Bamboo is scalable."

"The most valuable features are compiling and deployment."

"It's one of the best solutions in this line of work. We have many Atlassian products. We use Bamboo, JIRA, Service Desk, and some other Atlassian plugins. We like that it's easy to integrate into each other. It's a suite of services."

"The most useful feature of Bamboo is its integration with other solutions such as Jira and BitBucket, also offered by Atlassian. It is easier to use tools all provided by one vendor."

"The most valuable feature of Bamboo is that it is a good tool for CI/CD integration."

"One of the big things that made us choose Bamboo, is it seamlessly integrates its APIs into NetSuite, which is our main ELP system."

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

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

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

"Tekton's inclusion in Kubernetes deployment offers better visibility on how Tekton is performing within a cluster. It is lightweight and not as heavy as Jenkins to maintain."

"The flexibility of Tekton is the most valuable feature"

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

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

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

"Bamboo can improve by providing more with scripting, such as they have with Jenkins. Bamboo is more UI-driven at this time, Jenkins is going in that direction too."

"The tool is not capable of using YAML efficiently."

"The solution needs to support more customization in the training. What's offered is pretty generic. They need better training and should offer more guidance."

"It would be great if Bamboo could introduce a more containerized deployment model."

"Bamboo’s technical support services, in terms of speed of response, need improvement."

"It should be much easier to use. It shouldn't require a lot of reading to be able to use it. It should have just two or three screens rather than hundreds of screens requiring a lot of clicking. It also requires a lot of integration. It has a steep learning curve. It takes a lot of time to understand and put in the data. There is also no proper training."

"It can be challenging for someone new to the system or ecosystem to grasp, making it difficult to train new people and help them understand."

"Scalability depends on the use case. If it is really a big customer with a lot of tests, it might not be a scalable option for them."

"Tekton should have more accessibility for some rare use cases so that we can have more references when applying some techniques to our pipeline."

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

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

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

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

"It would be better if Tekton could show the YAML file while it is running, similar to GitHub pipelines, to provide more visibility on what's happening."

"Improvements could include introducing a UI-based pipeline development feature, such as drag and drop, which would help individuals with limited technical knowledge start building pipelines."

"Tekton could improve by adding better documentation."

"I rate the product’s pricing a five out of ten."

"The server products for small teams used to offer excellent pricing. However, Atlassian has since changed the offering and the pricing is more expensive. I do still think the solution offers good value for money."

"If Bamboo could provide more flexibility on pricing, that would help. On the agent side, if you want to increase the number of agents it should be less expensive. If they can provide some better pricing model, it will help, whether we are going to use it or are already using it."

"I rate the solution's pricing a three out of five."

"The price of Bamboo is reasonable."

"There is a subscription required to use Bamboo."

"Tekton is an open-source tool."

"The product is free of cost."

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

"The product is free and open-source."

"The solution is open-source."

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