New Features

None.

Feature Enhancements

None.

Resolved Issues

None.

Known Issues

Failure to load extremely complex Pipeline build records on Java 25

The workflow-completed/flowNodeStore.xml file records each step of a completed Pipeline build. If a build runs a very large number of distinct Pipeline steps whose arguments (such as the message passed to the echo step) include XML metacharacters such as > or ", this file includes a correspondingly large number of XML entity escapes. When running Java 25, if the number of such escapes exceeds 100,000, the build is not loadable from disk (for example, after a controller restart).


JUnit test results not displayed for large test reports on Java 25

Starting with CloudBees CI on modern cloud platforms 2.580.2.38434, Java 25 is the default Java version for the CloudBees CI container images. Java 25 limits the size of XML content that can be read to 100,000 characters. As a result, on controllers running Java 25, builds with large JUnit test reports might display no test results after the controllers restart. This mostly affects reports with long stack traces or a large amount of captured test output, which can exceed the 100,000-character limit. The test report page shows 0 tests, even though the results are recorded correctly. As a workaround, add the -Djdk.xml.maxGeneralEntitySizeLimit=0 and -Djdk.xml.totalEntitySizeLimit=0 Java options to the controller to remove the limit, and then restart the controller.


Duplicate plugins in the Operations center Plugin Manager UI

When you search for a specific plugin under the Available tab in the Operations center Plugin Manager, the search results show duplicate entries for the plugin.