CloudBees Jenkins Platform 2.32.3.1

Dependencies to plugins which were previously bundled on Jenkins WAR (detached plugins) are not resolved automatically. These plugins will have to be manually installed. More information

When renaming a folder, if clicking Apply instead of Save, a confirmation pop-up dialog is shown with duplicated header and footer. The workaround is to use the Save button

When a Client Master is straight deleted from a CJOC, the connection details are left behind. The workaround is to delete the CJOC connection details from the Client Master global configuration page

A second promotion of a job to a target instance which does not have RBAC configuration can fail with no replication permission. The workaround is to enable RBAC on the target instance or use groovy to remove the RBAC configuration from the promoted job

There is a timing issue when connecting a Client Master to a CJOC for the first time, using a custom update center. The recommended workaround is to associate the Client Master with CJOC without specifying the custom update center in a first step. Then, when done, configure the custom update center

When pushing connection details from CJOC to a clean CJE (along with SSO), the user gets logged in the Client Master as admin rather than as the user who started the configuration in CJOC. The workaround is to logout and login again.

When CJOC is enforcing the Role Based Access Control authorization strategy on client masters, the Groups detail screens on client masters will include two "Inherited from Jenkins" sections. The top-most section refers to the current master (which is a "Jenkins" but should be referred to as the connected master name shown in the breadcrumb bar) and the lowest "Inherited from Jenkins" section refers to CJOC (which is a "Jenkins"). The visual display of the information is less confusing when the masters have been organized using folders on CJOC as then the two "Inherited from Jenkins" sections are visually separated by the folders