CloudBees CI on modern cloud platforms 2.504.1.7

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

Under certain conditions, after applying a new Configuration as Code Bundle without restarting the controller (using the Reload Configuration option), users might see the following message in the Manage Jenkins section of the affected controller:

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.