CloudBees Jenkins Platform 2.277.4.2

2 minute read

RELEASED: 2021-05-05

Critical issues

Remove the jquery and jquery-detached plugins from your CloudBees Jenkins Platform instance

The jquery and jquery-detached plugins have been removed from all CloudBees Jenkins-based products and are no longer part of CloudBees Assurance Program. However, these plugins are not automatically uninstalled from your CloudBees Jenkins Platform instance as other plugins you use may still have dependencies on them. Please ensure that your CloudBees Jenkins Platform instance does not have any dependencies on these plugins, and then remove them. For instructions on how to check for dependencies in a particular plugin, refer to How to determine if a plugin is in use.

New features

Configuration as Code (CasC) bundles can be assigned to more than one controller (BEE-2275)

In the operations center, CasC bundles can now be assigned to more than one controller. Additionally, the administrator can globally change or modify the default bundle behavior, allowing a single configuration bundle to be used by all controllers. Once a bundle has been verified with one controller, it can be used across one or multiple controllers. This eliminates the need to create a new bundle each time you set up a new controller thus reducing time, manual error, and overhead. Assigning a bundle to more than one controller is a Preview feature.

The Availability pattern replaces the Master Path field. When upgrading, the Master Path is automatically translated to an Availability pattern, and the appropriate bundle is assigned to the controller from the controller configuration screen.

Feature enhancements

Configuration bundles are assigned to a controller in the controller configuration screen (BEE-1253)

To allow a configuration bundle to be assigned to one or more controllers, the assignment of a bundle to a controller has been moved from the Configuration as Code bundles screen to the controller configuration screen in operations center.

A new Bundle dropdown field is available in the controller configuration screen. The list of bundles is filtered using the Availability pattern from the Configuration as Code bundles screen.

The Availability pattern replaces the Master Path field. When upgrading, the Master Path is automatically translated to an Availability pattern, and the appropriate bundle is assigned to the controller from the controller configuration screen.

Resolved issues

Move/copy/promote log access (BEE-178)

Previously, users could access the move/copy/promote logs without the proper permissions.

This issue has been resolved. Now, only users with the privileges to trigger move/copy/promote operations can access the logs.

SNI support on ElasticSearch Reporter plugin (BEE-1630)

Before this change, HTTP communications were handled by an old version of async-http-client that didn’t support Server Name Indication (SNI).

The underlying http library has now been migrated to use okhttp, which does support SNI. This issue has been resolved.

Legacy terminology update (BEE-1606, BEE-1607, BEE-1608, BEE-1609, BEE-1612, BEE-1613, BEE-1623, BEE-1624, BEE-1625, BEE-1627, BEE-1628, BEE-2347, BEE-2393, BEE-2434)

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.”

Known issues

None.