Everything works well with deployment, application management, running jobs, and pipelines, and RBAC is effective. However, one area of concern is tracking license usage. With a ProCloud license, for example, there's no centralized console to monitor how many licenses have been used. This lack of visibility can lead to untracked consumption and potentially overshooting license limits. Additionally, we use the UAM plugin, but it doesn’t provide details on when users were added. This lack of tracking features is disappointing, especially given our status as a premium CloudBees customer. Better tools for monitoring license usage and user activities would be beneficial. We've noticed occasional issues with folder permissions changing unexpectedly. Specifically, permissions sometimes shift from the CloudBees user to the root user. This can cause pipeline failures, as pipelines require the correct CloudBees user permissions to execute properly.
We did face some challenges, particularly with the infrastructure. Our CloudBees Jenkins instances were deployed on virtual machines, and we experienced downtime in production environments. This downtime was often related to infrastructure issues rather than problems with CloudBees itself. CloudBees' team consistently advised us to maintain a robust infrastructure and ensure high availability to mitigate these issues.
One challenge I'd like to highlight is that with CloudBees CI growing bigger and bigger, there are limitations in terms of managing old plugins and services and upgrading them with time. There's always a priority thing that comes into the picture where you want something to be upgraded and fixed, but it all depends on how the priorities are set at the CloudBees side. As it is a proprietary tool, not an open-source tool, you always need to depend on the vendor. That is one challenge which I feel. It's not completely open source. Jenkins is an open-source software, but large organizations will rely more on proprietary software. And hence, you need to depend on them to manage the releases for their services, for their products, like for their plugins or for their features or whatsoever. So that is one thing which I feel is lagging a bit. But, overall, it's a great tool. It's a great service.
I noticed that CloudBees runs too slowly because some applications run more than 50 pipelines. When we try to open it, it takes too long and shows an error message saying the service is unavailable. While raising a case with the vendor, the vendor asks us to share the support bundle logs for the pipeline. When we try to download the support bundle logs, it still shows me the service unavailable error.
CloudBees DevOptics is a robust software utilized primarily to enhance CI/CD processes by offering real-time visibility into Jenkins pipelines. It facilitates effective monitoring, incident management, and decision-making through comprehensive data analysis. Users value its features like DevOps performance metrics and seamless tool integration, leading to improved operational efficiency and productivity in organizations.
Everything works well with deployment, application management, running jobs, and pipelines, and RBAC is effective. However, one area of concern is tracking license usage. With a ProCloud license, for example, there's no centralized console to monitor how many licenses have been used. This lack of visibility can lead to untracked consumption and potentially overshooting license limits. Additionally, we use the UAM plugin, but it doesn’t provide details on when users were added. This lack of tracking features is disappointing, especially given our status as a premium CloudBees customer. Better tools for monitoring license usage and user activities would be beneficial. We've noticed occasional issues with folder permissions changing unexpectedly. Specifically, permissions sometimes shift from the CloudBees user to the root user. This can cause pipeline failures, as pipelines require the correct CloudBees user permissions to execute properly.
We did face some challenges, particularly with the infrastructure. Our CloudBees Jenkins instances were deployed on virtual machines, and we experienced downtime in production environments. This downtime was often related to infrastructure issues rather than problems with CloudBees itself. CloudBees' team consistently advised us to maintain a robust infrastructure and ensure high availability to mitigate these issues.
To use the tool, you need to be familiar with the tool itself and with how it will be incorporated into the culture.
One challenge I'd like to highlight is that with CloudBees CI growing bigger and bigger, there are limitations in terms of managing old plugins and services and upgrading them with time. There's always a priority thing that comes into the picture where you want something to be upgraded and fixed, but it all depends on how the priorities are set at the CloudBees side. As it is a proprietary tool, not an open-source tool, you always need to depend on the vendor. That is one challenge which I feel. It's not completely open source. Jenkins is an open-source software, but large organizations will rely more on proprietary software. And hence, you need to depend on them to manage the releases for their services, for their products, like for their plugins or for their features or whatsoever. So that is one thing which I feel is lagging a bit. But, overall, it's a great tool. It's a great service.
I noticed that CloudBees runs too slowly because some applications run more than 50 pipelines. When we try to open it, it takes too long and shows an error message saying the service is unavailable. While raising a case with the vendor, the vendor asks us to share the support bundle logs for the pipeline. When we try to download the support bundle logs, it still shows me the service unavailable error.