CloudBees Jenkins Platform 2.289.1.2

Previously released as a Preview feature, specifying an Availability pattern to assign a bundle to more than one controller is now fully supported. For more information, see Configuration as Code.

In operations center, the Configuration as Code bundles screen now includes Used by and Available for columns that allow you to easily determine:

You can now simplify CasC bundle composition and maintenance by creating a "child" bundle that inherits common configuration elements from a "parent" bundle. This allows you to maintain common configuration elements in a single parent bundle that are automatically inherited by all bundles in the inheritance chain. This eliminates the need to manually maintain and update individual bundles. CasC bundle inheritance is a Preview feature. For more information, see Configuration as Code.

In operations center, a Default bundle option is now available in the Configuration as Code bundles screen to allow you to pre-select a CasC bundle in the controller configuration screen when setting up a new controller. For more information, see Configuration as Code.

CasC bundles now support storing configuration settings within subfolders for: jcasc, items, rbac, and plugins. The plugin catalog does not support more than one file.

The CasC bundle version number is automatically generated based on the content of the files to avoid potential problems during a configuration bundle update.

In operations center, the link file details and download link are now available in the controller’s Manage screen. Previously, the link file and download link were available from the Configuration as Code bundles screen. For more information, see Configuration as Code.

The list of events and their properties sent to CloudBees for purposes of tracking CloudBees CI product usage patterns was duplicated in an internal document and in the CloudBees documentation, but neither document precisely matched the actual behavior in the product. It was difficult to keep all sources synchronized, and some events or properties applied only to preview features or software versions not yet released.

When a controller was moved to a new location in operations center using Move/Copy/Promote, the controller loses the relationship with its CasC bundle if the new location is not matched by the Availability pattern.

New navigation selections for CloudBees CI and CloudBees Software Delivery Automation were incorrectly added to the CloudBees Jenkins Platform UI.

If an existing bundle was removed from operations center when the instance is not up and running, its access control configuration remained in the configuration files and the bundle was still in memory.

If the Availability pattern was changed and no check was executed, it was possible to reduce the visibility of the bundle, making it unavailable for the controllers using it.

GUI displays may have been slow to render when using GitHub multibranch projects due to the propagation of credentials from operations center to a controller while deciding whether to display a link to convert authentication to a GitHub App.

When a bundle was removed from operations center, added to operations center, and then removed from operations center a second time, all former associates with the bundle were retained and an error was returned.

When a new CasC bundle is added to operations center or an existing bundle is updated, the bundle was not properly updated.

A link to a missing JavaScript file caused a WARNING message in the logs when the Configuration as Code bundles screen was accessed.

When security access tokens were created, they were not visible, and the ConfigurationMap/Secret was not properly created when the controller was provisioned.

If using CloudBees CI 2.277.4.2 or 2.277.4.3, and you issued the casc-bundle-set-master CLI command, no CasC bundles were available to assign to the controller and an error was returned.

When a new version of a bundle is detected and downloaded, an error occurred when the bundle folder was deleted, which prevented the bundle from being updated. This issue has been resolved.

When a Configuration as Code (CasC) bundle with multiple files in a section was downloaded, the content of all files was overwritten with the content contained in the first file. This issue has been resolved.

A URI could not be used as value of the jcasc system property when the target is a folder instead of a file. This issue has been resolved.

This issue has been resolved. The casc-bundle-set-master CLI command now returns the correct information.

The github-branch-source plugin experiences high lock contention due to excessive and incorrect rate limit checking.

The LDAP server incorrectly uses string equality to check a DN.

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

A rendering issue was causing an HTTP 500 error that prevented the stand-by node page from loading properly on stand-by operations center or controller instances.

In some circumstances, while browsing shared agents, the user interface became non-responsive and created blocking issues for build-related objects.