CloudBees CI on modern cloud platforms 2.414.1.4

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

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.

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.

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

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.

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

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

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.

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

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.

Since the AWS Load Balancer Controller version 2.4.3, the HTTP to HTTPS redirection does not work anymore. The issue is now fixed. The redirection is now set up using the alb.ingress.kubernetes.io/ssl-redirect annotation.

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.

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.

The CloudBees CI Helm Chart schema is incorrectly formatted and it causes the following sections to be missing: Master, Agents, Persistence, Hibernation, PodSecurityPolicy, NetworkSecurityPolicy, rbac, Common. And consequently make the validation ineffective. The issue has been fixed. The values schema contains all of the relevant sections for validation.

There was a syntax error in the sidecar-injector Helm template. This issue has been fixed.

The action from the operations center to quiet down an managed controller could hang and acquire a lock that would prevent other operations from running on the managed controller. This issue is resolved. A lock is no longer acquired.

There was a syntax error in the sidecar-injector Helm template helpers. This issue is resolved.

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

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.

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.