CloudBees CI on modern cloud platforms 2.504.1.7

When upgrading or restarting CloudBees CI, the controller or operations center fails to start and returns a Messaging.afterExtensionsAugmented error. The operations center can also fail to start with an OperationsCenter.afterExtensionsAugmented error. Refer to CloudBees CI startup failure due to IndexOutOfBoundsException related to corrupt messaging transport files for a workaround for this issue.

If a managed controller is installed in its own namespace and Agents.SeparateNamespace.Enabled=true is passed to the Helm chart or included in the custom values file, all agents will run in the cbci-builds namespace by default, where cbci is the namespace of the operations center, and the agents are not installed in a namespace corresponding to the managed controller. This also prevents agents with service accounts from being installed in a namespace corresponding to the managed controller, and could potentially lead to security vulnerabilities since a managed controller admin could tamper with agents for another managed controller.

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.

If a Declarative Pipeline build was running in version 2.492.2.3 (or earlier) and the controller was then upgraded to this release, the build would resume. However, if the controller was restarted a second time, the build would fail. This issue also impacts most running Declarative Pipelines during HA controllers rolling upgrades to this release. This issue is resolved when upgrading to 2.516.1.28662.

In CloudBees CI, links to search results for items nested within folders are broken. Pressing Enter after searching returns Nothing seems to match, while links to root-level items work correctly.