CloudBees CI on modern cloud platforms 2.452.3.2

Added a new HTTP endpoint to the Hibernation monitor. The new endpoint can be used by external health check systems to generate alerts when a controller is not healthy, without waking up the controller.

When possible, the SCM commit and commit message in the CloudBees Pipeline Explorer build info bar now link to that specific commit in the SCM repository.

The AWS Credentials defined in the HashiCorp Vault store in the Operations center were not usable in controllers.

In UsernamePassword credentials and in SSHCredentials, the CloudBees HashiCorp Vault plugin sent multiple requests to HashiCorp Vault to retrieve credentials information.

In Configuration as Code Plugin Management 2.0 (bundles with apiVersion: 2), you could define passwords and tokens using environment variables.

Optional logging allows the logging contents of the folders to be involved in the bundle checkout at every step of the process.

In the Configuration as Code (CasC) UI, where multiple bundles are present per bundle location, the bundles are now shown in alphabetical order.

The support bundles that are generated from the High Availability (HA) controllers now include, by default, a list of Hazelcast structures and associated statistics that can be useful to diagnose delayed communication between replicas, buffering issues, excessive memory usage, and so on.

The API tokens created on controllers with the operations center SSO enabled were lost on first usage. They are no longer revoked if the user configuration option Synchronize details on login is disabled.

In the CloudBees Pipeline Explorer, various elements positioning have been improved. These elements are: the BFA indicator, the search input when there is an error, and badges that display the log and map.

Prior to this fix, the CyberArk credentials within a CloudBees CI instance were not removed when applying a CasC bundle with CyberArk credentials to that instance.

When using Configuration as Code (CasC), if a controller is configured against the operations center, but has no associated bundle, the request for a linkfile returns a 400 (bad request) error instead of 200 (ok) error.

When multiple Pipeline policies or rules were run, the list of policy violations might be displayed in an arbitrary order. Now, the order should be predictable.

When updating the Configuration as Code bundle version number while hot reloadable plugins were present resulted in a NullPointerException error.

When using credentials in the Kubernetes Cluster Endpoints configuration, the Validate functionality shows an Angry Jenkins in the UI and a NullPointerException in the logs.

A NullPointerException caused noise in the logs that prevented an item that recently left the queue to be proxied.

An Admin Monitor checking Backup Projects for security issues led to possible locks in the RBAC cache.

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

Clouds deselect after a user without Administer permissions edit the Folder configuration.

The NonConfigurableKubernetesCloud setting on the pod template page appeared to be editable. However, it is read-only.

The Git plugin now uses JGit with Apache MINA only as SSH transporters.

The commons-lang3 library is no longer bundled with the infradna-backup plugin and the dependency now uses the commons-lang3 plugin.

The following plugins have been added to the Operations center CloudBees Assurance Program since 2.452.2.3:

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