CloudBees CI release highlights

What’s new in CloudBees CI 2.414.1.4

Watch video

New Features


Feature Enhancements

The User Activity Monitoring plugin improves unique user count

The User Activity Monitoring plugin now counts unique users based on the user’s email address and the user name. Refer to Counting and monitoring user licenses with the CloudBees User Activity Monitoring plugin for more information.

Quiet Start Plugin can be used with Configuration as Code

Quiet mode could only be activated through the UI. Now, Quiet mode can be activated in both the UI and CasC. Refer to Quiet start for more information.

CloudBees Pipeline Explorer expand page view

As a Pipeline Explorer user, I want the ability to display more of my logs without the Jenkins overhead. The user can now use fullscreen mode to expand the view of the CloudBees Pipeline Explorer and display more log lines.

Easier to select text in CloudBees Pipeline Explorer

As a pipeline user, I want the ability to select text from a line. There is now an improved experience to select text and lines in the main log view of the CloudBees Pipeline Explorer.

Update to view stage selection model in CloudBees Pipeline Explorer

In the tree view stage selection model, a click now triggers filtering, just like clicking on the funnel icon. The double-click expands and collapses the node (it was previously a click).

Contextual linking from pipeline steps view to CloudBees Pipeline Explorer

The Pipeline Explorer is now accessible from the pipeline steps view. All of the steps displayed through the pipeline steps view provide a link to the Pipeline Explorer with the active filter and line, if available.

Pipeline Explorer - Shortcuts

In the Pipeline Explorer, add the ability to display the keyboard shortcuts. The keyboard shortcuts are now available to the CloudBees Pipeline Explorer users.

Allow users to see which Jenkins Java methods are called from Pipelines

Support bundles can now include a new list of Pipeline projects whose last completed build made these calls, including a list of details.

Resolved Issues

Reduce the amount of save requests when updating controllers with CasC

When a connected controller is updated with CasC, only one save request will be made to update all of the properties, so only a minimum number of operations will be performed to update a controller.

Direct links to search results in CloudBees Pipeline Explorer open favorite drawer

In the Pipeline Explorer, the use of a direct link to a search page opened the user’s favorite drawer. Now, if you use a direct link to a search page, it does not open the user’s favorite drawer.

The pipeline-stage-view plugin installed as part of the suggested plugins list

The pipeline-stage-view plugin was removed from the suggested plugins list in the previous release, but was still installed due to transitive dependency in the CloudBees Pipeline Stage View Extensions plugin. The CloudBees Pipeline Stage View Extensions plugin is now also removed from the list of suggested plugins.

Previously created backup and restore jobs fail after Backup plugin update

After updating the Backup plugin to version 3.38.60 or later, backup and restore jobs created before the update (that also used the Remote SFTP server) would fail with a NullPointerException unless the job configuration was resaved. This issue is resolved.

Prevent deadlock when the websocket connection between a controller and the operations center is closed

A deadlock may result when a controller’s connection to the operations center was disrupted and the controller was connected using web sockets. This causes the connection to be unusable and the controller will not reconnect until it is restarted.

Download of Plugins / Core is logged as successful before the start of the download

When downloading Plugins or Core version from an Update Center item page, the plugin would display a "Successful download" in the system logs before the download actually started. The issue has been fixed. The success of the download is logged after completion.

Configuration for JDK provided in the CloudBees CI MSI distributable allows weak TLS algorithms

Added weak TLS algorithms to jdk.tls.disabledAlgorithms in conf/security/ of the provided JDK. Additionally, OpenJDK JRE was updated to version 11.0.19-7.

Known Issues

Failed parsing of data in the User Activity Monitoring plugin leads to incomplete data

Failed parsing of data from the User Activity Monitoring plugin will overwrite the user activity database. All user activity data that is logged up to that point in time is lost, in order to avoid this, refer to this knowledge base article Why is my user activity missing?.

HTTP Client used for Operations Center to Controllers connection leads to performance issues

Because of known issues in the Java HTTP Client, there could be performance issues in Operations Center to Controllers interactions in heavily loaded environments.

More details about this issue and workarounds are documented in Operations Center Client leaks HTTP Clients since version 2.401.1.3.

Older versions of controllers cannot start after receiving new bundle versions

When the operations center sends new bundle versions to controllers older than 2.401.1.3, the controller cannot start.

This issue does not affect controllers in version 2.401.1.3 or newer.

There are three ways to fix the issue:

  • Upgrade all controllers to version 2.401.1.3 or newer.

  • Stop configuring controllers in versions prior to 2.401.1.3 using CasC.

  • Install a Plugin Catalog on the operations center with a beekeeper exception to install cloudbees-casc-server:2.5.1. The Plugin Catalog can be enabled in operations center by setting the system property Dcom.cloudbees.jenkins.cjp.installmanager.CJPPluginManager.enablePluginCatalogInOC=true.

When CloudBees Pipeline Explorer was enabled, some pages were very slow for complex Pipelines, leading to controller-wide performance issues in some cases

Error when renaming an existing EC2 cloud

When the name of an existing cloud node is updated, the user receives a 404 error after selecting save. This is because the cloud page uses the cloud name as part of its URL. When the user saves the name, Jenkins sends the user to the URL with the old cloud name. Please note that all node changes are saved successfully.

Duplicate Pipeline Template Catalogs in the Configuration as Code (CasC) for Controllers jenkins.yaml file on each instance restart

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