CloudBees CI on modern cloud platforms 2.319.3.3

A new Configuration as Code bundle location setting has been added to the Manage Jenkins  Configure System screen and allows you to configure a local folder on the operations center server or an SCM repository for adding controller CasC bundles to the operations center’s internal storage.

The minimum version of Kubernetes required to run CloudBees CI on modern cloud platforms is now 1.19. Support for older versions of Kubernetes is dropped. Refer to the Supported platforms for CloudBees CI on modern cloud platforms for more information.

The frequency of sidecar injector’s certificate renewal check was reduced from daily to once every two weeks.

Helm v3 lets you validate Helm chart values in a chart’s values.yaml file using JSON schemas, which can be a useful way to validate input values.

When using a Java system property to configure a client controller using the casc-bundle-link.yaml file, the client controller’s connection details are now included in the client controller’s jenkins.yaml file and the client controller is automatically connected to the operations center.

Previously, HTTP communication was managed by an old version of async-http-client.

You can now use dynamic PVC for any volume declared in a pod template using the Kubernetes plugin.

The plugins.yaml file in a CasC bundle is now validated to ensure plugins can be installed by verifying that all plugins included in the plugins.yaml file are in the CloudBees Assurance Program (CAP) as a Tier 1 or Tier 2 plugin. If a Tier 3 plugin is included in the plugins.yaml file, a validation is performed to verify the plugin is also included in the plugin-catalog.yaml file.

The following CasC bundle validation processes have been improved and new CasC bundle validations have been added. If any of these conditions are not met, a validation error is returned.

CasC bundle validation messages have been improved. A validation code has been added to help identify errors that occur when automation is configured to process log files. The details of the error are included in the log files.

When exporting the CasC items.yaml file from the Configuration as Code export and update screen or when exporting individual CasC items from the left navigation pane, the exported YAML properties are now ordered. The first property is kind, followed by name. All other properties are ordered alphabetically. Previously, the exported properties were not ordered in a deterministic way.

The following plugins were updated to be compatible with both current and upcoming Jenkins versions that have a newer Guava library.

If there were too many managed controllers in a namespace, every pod was allocated thirteen environment variables for each controller, the operations center, the hibernation monitor, or any other Kubernetes service in the namespace. These variables were generally unused and could bloat both the build log and the program.dat file in each build record, reducing performance.

Under certain conditions, including following a restore from a backup made using EBS snapshots, a Pipeline build could have been broken with the error message, ‘Unsupported protocol version 101’ with a stack trace mentioning ‘RiverReader.restorePickles’.

Attempts to create managed controllers using the operations center CasC items.yaml file often failed for new CloudBees CI installations the first time the operations center started, due to the initialization order of some plugins.

The internal library used by the CloudBees Analytics Plugin to manage event data was lacking proper logic to deal with backpressure, resulting in ever-increasing memory consumption in some circumstances, like being offline.

The Fabric8 Kubernetes Client was upgraded to version 5.10.1 for the open source Kubernetes Plugin. The Master Provisioning Kubernetes plugin was upgraded to use the latest release of the Kubernetes API client.

The Enable Agent > Controller Access Control toggle option was removed from the Global Security Settings. This option has been also been removed from Jenkins.

The Mesos Cloud plugin is no longer used by CloudBees CI, but there were some optional dependencies to it in the Operations Center Context plugin.

Users were incorrectly required to have Job/Configure permissions when selecting credentials for the non-blocking I/O SSH agent launcher.

The CloudBees SSH Build Agents plugin was using an outdated library to manage the SSH connection.

An error was occurring when a shared configuration contained a license usage alert. The license check would not persist in the shared configuration because controllers were being serialized with a class that is not allowed for XStream.

When checking the CasC bundle version using HttpLoader, bundle validations were triggered before the bundle was downloaded.

If you added more than one Jenkins configuration file to a CasC bundle that already contained a Jenkins configuration file, and then attempted to reload the configuration without restarting, the new Jenkins configuration files were ignored.

Under certain conditions, if a Pipeline build was interrupted by a controller restart or a backup/restore, it was treated as a general failure and the aborted build was not displayed in the administrative monitor when using the Restart Aborted Builds plugin.

Freestyle job Build Environment settings can now be exported and configured using CasC item creation.

The Download icon on the Export CasC item screen was broken.

If a GitHub Multibranch repository or organization folder did not use credentials and attempted to access public GitHub repositories via an anonymous API, a NullPointerException may have been returned.

The SSE Gateway Plugin was transitively listing a version of follow-redirects that had a known vulnerability. The library was updated to a version that does not contain the issue.