I like that CloudBees makes it easy to centralize CI/CD pipelines.

The no-code platform approach is nice for getting started, but it can sometimes be hard to use in practice.

It also connects well across standard enterprise toolchains for automated builds, releases, and feature management.

• Offers security-hardened Jenkins images, tested and verified plugins, Role-Based Access Control (RBAC), and continuous compliance features.

• Kubernetes Scaling: Supports elastic scaling and multi-master architectures running on Kubernetes Review collected by and hosted on G2.com.

I think CloudBees is very expensive, so it really needs to be set up as efficiently as possible to maximize its value. It also has a steep learning curve, and even experienced infrastructure engineers can find it challenging to switch CI/CD pipeline management systems. Having some AI, cloud, or coding skills—or better tools—to automate more of the migration from older systems to CloudBees would be extremely useful.

It also feels rooted heavily in traditional Jenkins models, which can come across as less native compared to more modern, GitOps-first CI/CD alternatives. On top of that, there are UI and search limitations: users occasionally mention clunky navigation, enablement materials that lag behind, and a dated documentation experience. Review collected by and hosted on G2.com.