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
- Duplicate Pipeline Template Catalogs in the Configuration as Code for controllers
jenkins.yamlfile on each instance restart -
If a Pipeline Template Catalog is configured in the Configuration as Code
jenkins.yamlfile and theidproperty is not defined, the catalog is duplicated on each instance restart and in the exported Configuration as Code configuration.
- 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.
- Inconsistencies between some Configuration as Code (CasC) features and High Availability (HA)
-
When using Configuration as Code in controllers that run in High Availability (HA) mode, the CloudBees Configuration as Code Export and Update screen may display inconsistent information about the bundle along with two buttons: Restart and Reload. This is caused by information not being properly synchronized between replicas. Furthermore, users may experience the following problems when trying to use one of the two buttons on that page:
-
Automatic reload bundle: clicking this button shows an error message.
-
Skip new bundle version: clicking this button forces a restart and the instance will not start again.
-
While the fix for this issue is being worked on, we recommend the following if you are using Configuration as Code in controllers that run High Availability (HA):
-
Controllers that have configured the automatic reload. Users must disable it and configure the automatic restart instead.
-
Controllers that do not have any automation (Bundle Update Timing). Users must stop using the Reload button and start using the Restart button instead.
- 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
-webSocketon 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.
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)
-