CloudBees CI on modern cloud platforms 2.541.3.36065

The following plugins have been added to the operations center CloudBees Assurance Program since 2.541.2.35785:

The following plugins have been added to the controller CloudBees Assurance Program since 2.541.2.35785:

CloudBees CI now supports service accounts, which authenticate automated processes without using personal user credentials. Service accounts are independent of individual users, integrate with Role-Based Access Control (RBAC) for permission management, and support token rotation for enhanced security. Define service accounts at root scope for global access or at item scope for team-level management. For more information, refer to Authenticate automated processes with CloudBees CI service accounts.

The rbac.groupName Helm value can now be used to bind controller management roles and cluster roles to a Kubernetes Role-Based Access Control (RBAC) group. This enables integration with Amazon Elastic Kubernetes Service (Amazon EKS) access entries for identity-based authentication against secondary managed controller clusters. When used with Agents.SeparateNamespace.Enabled: true, the Kubernetes RBAC group is correctly applied, and created controller service accounts are configured with the required permissions.

An administrative monitor now alerts administrators when agents are using an outdated remoting library or a JDK version older than the controller JDK version. The monitor includes a link to a page listing all outdated agents.

Personal Slack notification titles are now more compact and include a build status icon, ensuring the status is always visible.

Personal Slack notifications for completed builds now include both the job name and build number in the message summary. Previously, only the build number was shown, making it harder to identify which job the notification referred to.

In multi-cluster environments with the hibernation monitor enabled, external managed controllers were properly hibernated, but the hibernation redirect URL pointed to an incorrect hostname.

Previously, when using the CloudBees SSH Build Agents plugin (cloudbees-ssh-slaves) with a manually specified host key, the connection could have been refused if the server’s first proposed key algorithm did not match the algorithm of the manual host key, even if the key itself was valid.

When the controller URL pattern is set to HTTPS, the CasC Controller Bundle Service was unable to notify controllers of updates. A new Helm chart value, Master.tokenReviewEnabled, has been added to control creation of the Kubernetes tokenreview ClusterRole and ClusterRoleBinding. This value must be enabled for multi-namespace installations to allow update notifications.

Controllers could sometimes hang during shutdown or restart due to analytics-related shutdown processing in the CloudBees License Tracker plugin (cloudbees-license-tracker). This issue has been resolved, and instances now shut down and restart as expected.

Java 17 is supported through the March 2026 release; support will be removed starting with the April 2026 release. You will need to migrate to Java 21 to continue using CloudBees CI after March 2026. An administrative monitor has been added to notify you if either the operations center or any connected controllers are running with Java 17. If you have any concerns or questions, please contact CloudBees Support.

When you search for a specific plugin under the Available tab in the Operations center Plugin Manager, the search results show duplicate entries for the plugin.