CloudBees CI on modern cloud platforms 2.414.3.8

The following security tickets were fixed from Jenkins:

On the Configure Controller Provisioning page, the YAML file is not validated when it is configured in the Default YAML field.

When using "Auto-update bundle version", the wrong bundle may be updated if multiple bundle.yaml files exist in the repository.

The .wrappedToken file is inadvertently being included in the bundle by the operations center bundle retriever and giving a structural warning, [STRUCTURE] - The following files have been detected in the bundle folder but they are not yaml files: .wrappedToken.

When a bundle is retrieved from the SCM there are benign warnings in the logs about communication with the operations center.

When the name of an existing cloud node is updated, the user receives a 404 error after selecting save. This is because the cloud page uses the cloud name as part of its URL. When the user saves the name, Jenkins sends the user to the URL with the old cloud name. Please note that all node changes are saved successfully.

If a Pipeline Template Catalog is configured in the CasC jenkins.yaml file and the id property is not defined, the catalog is duplicated on each instance restart and in the exported CasC configuration.

The following plugins have been removed from the Operations center CloudBees Assurance Program since 2.414.2.2:

The following plugins have been added to the Controller CloudBees Assurance Program since 2.414.2.2: