Bamboo vs Tekton comparison

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

"The most valuable features are compiling and deployment."

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

"In Bamboo, build and deployment have been segregated. The build plan and deployment plan are different. When comparing Bamboo to other solutions, the native feature you will not find in another tool, such as Jenkins. They have segregated the build and deployment plan. This means, building the application and deploying it are two separate parts in Bamboo, they have segregated it apart from the UI. This makes the tool a bit better compared to other tools."

"In my experience Bamboo is scalable."

"We use Bamboo to automate all our test builds and deployments. It integrates with tools like the ReportPortal to help us check and evaluate processes. When we initiate commands, it automatically checks for scaling issues or failures related to new code. Based on these evaluations, it provides reports in the ReportPortal, helping us decide whether to implement changes."

"It can do the CI pipeline well."

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

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

"Tekton is a stable product."

"It is an open-source tool, which makes it highly adaptable."

"The tool offers flexibility and compatibility."

"Tekton's most important feature is its cloud-native nature. Unlike Jenkins, which may not scale as efficiently, Tekton's CI pipeline can automatically scale up to handle increased workload demands without needing manual adjustments."

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

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

"I like the setup of the dashboard."

"Bamboo is a bit complicated to use compared to other solutions, such as GitLab. You have to integrate different actions that are difficult that could be made easier."

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

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

"Integrating workflows with other platforms can be challenging. The capabilities of these platforms sometimes fall short compared to others. Initially, it was difficult for us because the plugins were very limited."

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

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

"Bamboo could improve by having compatibility with GitLab. It would be better to have this platform for deploying code and storing container registries. Bamboo does not have a container registry. Additionally, there could be more features added."

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

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

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

"Tekton could improve by adding better documentation."

"The user interface of Tekton could be improved."

"Improvement is needed in the build step."

"The product's UI could be improved, as there are occasional latency issues. The triggering part, especially the CRD installation needs enhancement."

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

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

"The price of Bamboo is reasonable."

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

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

"There is a subscription required to use Bamboo."

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

"The product is free and open-source."

"The solution is open-source."

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

"Tekton is an open-source tool."

"The product is free of cost."

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