CloudBees is pleased to announce this CloudBees CD/RO patch release (download page). You can find specific information about this release in the following sections:

This patch release supplies:

For all other changes in v2025.09.1, refer to the CloudBees CD/RO v2025.09.0 release notes.

Before upgrading to v2025.09.x from v2025.06.0 or earlier, there may be several upgrade notes that require action on your part. For more information, refer to the CloudBees CD/RO v2025.09.0 Upgrade notes.

Security fixes

The following security fixes and improvements have been made as part of this release:

JSPDF dependency updated to address security vulnerability

The JSPDF library has been upgraded to a newer version to resolve a known security vulnerability and ensure improved application security.

New features

The following new features are introduced as part of this release:

Feature enhancements

The following feature enhancements have been made as part of this release:

Increased limit for group fields in analytics reports

This update increases the supported number of fields in group by aggregations to 15 when creating analytics reports.

Resolved issues

The following issues have been resolved as part of this release:

Improved CloudBees CI event handling in clustered environments

Fixed an issue in clustered {PROJECT} environments where CloudBees CI events were processed across multiple nodes, resulting in duplicate or inconsistent job and build records. With this update, each service instance now processes events from a payload through its own dedicated queue, ensuring consistent, single-node processing and preventing duplicate or out-of-order job and build entries.

Fixed SSO authentication failure caused by misconfigured AD query user credentials

Resolved an issue where Single Sign-On (SSO) authentication failed when the query user credentials were incorrectly configured in Active Directory (AD) providers. With this fix, misconfigurations no longer interrupt the SSO authentication flow.

Fixed resource scaling issue during job execution

Resolved an issue where resources could scale down while a job was still running. Resource allocation now remains stable throughout job execution, improving overall performance and reliability.

Known issues

The following issues are included as known issues in this release:

ACLs not applied to nested objects

ACL details are not applied to nested objects within a root object.

DeployerApplication changes not applied via YAML DSL sync

Rearranging or modifying DeployerApplication objects using YAML DSL sync does not work because the deployerApplicationName is not set.

Validation error when creating EnvironmentTemplateTierMap via YAML DSL sync

Creating an EnvironmentTemplateTierMap using YAML DSL sync can fail with a validation error because the name field is missing in the metadata.

Renamed objects not removed after reapplying YAML DSLs

When YAML DSLs are reapplied after renaming objects, the previously defined objects are not automatically removed and remain in the system.

ACL inheritance incorrectly applied to empty PropertySheet in YAML dslsync objects

An empty PropertySheet generated through YAML dslsync may incorrectly include ACL inheritance information.

Incorrect YAML indentation for multi-line gateCondition in gate tasks

When multi-line command or source code is added to the gateCondition of gate task objects, the generated YAML may have incorrect indentation.

Group tasks generated through YAML DSL sync not nested

Group tasks created using YAML DSL sync do not form a nested structure as expected.