New Features

None.

Feature Enhancements

None.

Resolved Issues

Cannot use the publishIssues step outside of an agent

The publishIssues step returned an exception when run outside of any node block (that is, when not using an agent). This is now fixed and it can again be used in any context.


Reconfiguring static inbound WebSocket agent improperly added blank tunnel

After reconfiguring a static inbound agent in the GUI using fields such as WebSocket deprecated in 2.440.x, the suggested launch instructions would incorrectly include -tunnel (with no argument) even if that field had been left blank.

Known Issues

Saving shared cloud from GUI lost WebSocket checkbox

If a shared cloud (as opposed to a single agent) was defined in 2.426.x (or earlier) with an inbound launcher and a specific launch configuration, particularly the Use WebSocket checkbox (also tunnel and custom work dir settings), configuring and resaving that cloud in the GUI in 2.440.x will silently drop that configuration, potentially breaking a working setup.

As a workaround, avoid resaving such shared clouds using the GUI. Use Configuration as Code with YAML or REST or CLI with XML if some unrelated aspect of the cloud needs to be adjusted.


Inbound shared agents aligned with new Remoting CLI options

Certain options for the inbound agent launcher, particularly the checkbox for WebSocket, were removed from the configuration GUI in 2.440.x, in favor of passing the corresponding option such as -webSocket on the CLI. In the case of inbound shared agents or clouds, this did not suffice since the operations center was responsible for launching the cloned agent that connects to the controller. This makes it impossible to create new shared agents or clouds using WebSocket transport via GUI configuration.

As a workaround, configure fields, such as webSocket, in the agent/cloud launcher definition via Configuration as Code YAML or REST or CLI upload of XML; or copy a working agent/cloud item instead of creating one from scratch.


Duplicate Pipeline Template Catalogs in the Configuration as Code for controllers jenkins.yaml file on each instance restart

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


Error updating the plugin installation report prevent the bundle from being applied

New Configuration as Code bundle versions installing new plugins cannot be reloaded. An error appears and the new bundle is not applied. If the Configuration as Code bundle has new plugins to install, the instance must be restarted.

Upgrade Notes

Operations center CloudBees Assurance Program plugin changes since 2.440.2.1

The following plugins have been added to the Operations center CloudBees Assurance Program since 2.440.2.1:

  • CloudBees Platform Insights Plugin (cloudbees-platform-insights)


Controller CloudBees Assurance Program plugin changes since 2.440.2.1

The following plugins have been added to the Controller CloudBees Assurance Program since 2.440.2.1:

  • CloudBees Platform Insights Plugin (cloudbees-platform-insights)