CloudBees Jenkins Platform 2.332.1.4

CloudBees CI Docker images are now published with a signature, allowing you to verify their origin and authenticity.

A new Default version field has been added to the Configuration as Code bundle location on the Manage Jenkins  Configure System screen. It allows you to specify the default version (a branch, tag, or commit) to check out controller CasC bundles from the SCM repository.

Operations center CasC bundle validation messages have been improved. CasC bundle validation codes has been added to help identify errors and warnings. The error and warning details are included in the operations center log files. This can useful if you have automation configured to parse the log files and identify problems. For more information, refer to Troubleshooting CasC for the operations center.

The items.yaml file within the CasC Bundle is now validated to verify:

The CasC bundle inheritance validator now verifies that the controller CasC bundle that is defined as the parent in the bundle descriptor exists at the same file system level as the child bundle. For more information, refer to Troubleshooting CasC for controllers.

The jenkins.yaml file within the CasC bundle is now validated to verify:

The plugin-catalog.yaml file within the controller CasC bundle is now checked, to verify the plugin catalog is valid in the instance. For more information, refer to Troubleshooting CasC for controllers.

A new message was added to the Administrative Monitor to encourage you to upgrade to Java 11 as soon as possible. The message will display if your CloudBees Jenkins Platform instance is not already running Java 11. The message states the following:

Support for Java 11 was added in this version. CloudBees recommends that you upgrade your instances to Java 11 as soon as possible for the best experience.

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

In version 2.319.2.5, the default encoding for images was configured as ANSI_X3.4-1968, rather than UTF-8. This may have resulted in encoding issues in Jenkins.

If you use a local folder as the Configuration as Code bundle location and an error occurs, a backup folder is automatically added to the operations center. Previously, if the local folder contained other files that were not part of a CasC bundle (for example, read-only files, hidden files, or SCM control files), polling synchronization failed and the backup folder was never deleted. Eventually, the operations center may have ran out of disk space, resulting in a No space left on device exception.

Under certain conditions, the number of threads used by the Metrics plugin continually increases, leading to performance issues on the controller.

When a user could not be found in the operations center security realm, it caused excessive logging in a controller’s log.

A JavaScript error was shown in the Advanced tab on the Plugin Manager page.

When trying to configure a REST API call post build action, the Add parameter UI did not work.

Some of the product WAR files were bundled the same artifact at different versions. This led to several issues, depending on the operating environment and the library that was provided by the web container.

In some situations, when using a GitHub Enterprise server organization, scanning failed with a NullPointerException.

This issue has been resolved. The icon is now properly displayed.

Some security realms, such as SAML, are not able to resolve groups. This caused the Role-Based Access Control Plugin to migrate ambiguous member entries to users instead of leaving them ambiguous, to be resolved by the end user.

Groovy in Jenkins core was updated to 2.4.41, which caused an issue when renaming or moving CloudBees Template instances.

CloudBees has determined that an upcoming change to the Update Center in Jenkins Core 2.330 could potentially break functionality for the CloudBees Unified UI Plugin.

CloudBees is updating terminology to remove offensive text. During this ongoing initiative, “controller” replaces “master,” “agent” replaces “slave,” “allowlist” replaces “whitelist,” and “denylist” replaces “blacklist.”

Two metrics, kubernetes-client.connections.running and kubernetes-client.connections.queues, were removed from the Kube Agent Management plugin to ensure compatibility with the latest version of the Kubernetes plugin.

The javax.mail packages were removed from Jenkins core in version 2.331. The CloudBees Jenkins Enterprise License Entitlement Check was using one of the packages to validate email addresses.

When you sort the list of plugins in the CloudBees Plugin Manager, duplicate badges display by the title of the plugin.

When you viewed a GitHub organization folder, the Create GitHub App item in the left navigation displayed as a broken icon.

The Jenkins community will begin supporting Java 11-specific features soon (Java 11 byte code), at which point it will no longer be possible to use a Java 8 runtime environment. Because CloudBees Jenkins Platform is based on the Jenkins LTS, future releases of CloudBees Jenkins Platform will have the same requirement.

The minimum required Jenkins version was updated to the latest LTS, version 2.332.1.

Garbage collection has been updated in Java 11. Many of the previously recommended arguments are no longer supported. When you upgrade your JDK to Java 11, you must also update your garbage collection configuration. Using unsupported Java arguments will result in startup failure.

Jenkins 2.326 removes the ability to disable or customize the agent-to-controller-security system. The following plugins are known to be affected by this change:

Version 3.0 of the Matrix Authorization Strategy plugin extends the formats for permission assignments both internally and when used with the Job DSL and Configuration as Code plugins. With the upgrade to version 3.0, all past permission assignments are now considered ambiguous. While existing configurations can still be read, if the permission assignment configurations contain ambiguous entries, warnings will appear in the UI and in logs.