CloudBees CD/RO v2025.09.0

Fixed path traversal vulnerability that could allow an attacker to read arbitrary files from the server.

To address security vulnerabilities, the kubectl version included in agent images was updated to v1.33.0.

To address multiple vulnerabilities, the jsPDF library used by CloudBees CD/RO has been updated to v3.0.1.

To address security vulnerabilities, Apache Commons VFS2 was updated to v2.10.0.

To address security vulnerabilities, the Spring Security module was updated to v6.4.5.

To address security issues, OpenSearch was updated in CloudBees Analytics from v2.19.0 to v2.19.1.

To address security vulnerabilities, the Helm version included in agent images was updated to v3.18.0.

A path traversal vulnerability was identified, in which unsanitized input from the request URL could be used directly as a file path. This could allow attackers to craft malicious requests that access unauthorized files or directories outside the intended location.

To address security vulnerabilities, the kubectl-argo-rollouts version included in agent images was updated to v1.8.2.

To address security vulnerabilities, the ion-java library was updated to v1.10.5.

Added a Notification option in stages with a pop-up that includes Recipients, Email Notification Preview, Email Configuration, and Save/Cancel controls. Mandatory fields (Recipients and Email Configuration) must be completed when a notification type is selected. The Save option is enabled only after mandatory fields are filled; otherwise, Cancel remains available.

Added an All components filter next to the Projects and Applications filter, allowing users to filter the environment inventory list by components.

Tasks that are skipped due to pre-condition not met will be highlighted with "Skipped, Pre-condition not met" message.

Users can now configure the maximum lifetime of access tokens up to 9999 days through the UI. Setting a token with a long duration remains possible but increases the risk of unauthorized access if the token is exposed.

Added support for specifying an external script file path in commands, as an alternative to embedding Groovy code inline. The script runs in the same context as inline scripts, and logs and error messages now display the script file name for easier debugging.

Job logs now remain accessible even after custom autoscaling operations scale down resources. This ensures users can continue to debug, monitor, and audit jobs regardless of resource termination, improving reliability and traceability in dynamic environments.

A new “Include Plugin projects” checkbox has been added to the Procedure List page. When selected, this option will display procedures from plugin projects in addition to standard procedures.

The Duration Time field has been updated to improve flexibility and input precision. Users can now manually enter the duration in HH:MM format (24-hour clock). The field accepts values between 00:00 (minimum) and 23:59 (maximum).

Admin users now have the ability to restrict other users from logging in by username and password and enforce them to use SSO login.

Added REST API endpoint for sending emails, supporting authentication and authorization consistent with other endpoints. Responses follow REST conventions, and the endpoint is documented in the official REST API documentation. Functionality matches the existing sendEmail method in ectool/ec-perl.

Added --format option to the dslsync generate and dslsync apply commands, supporting groovy and yaml outputs. If no format is specified, output defaults to Groovy for backward compatibility. YAML files are generated with correct syntax, preserving the folder structure used for Groovy. Currently, the “Project” object type is supported; other object types will be added in phase 2. For more information, refer to DSL Git Synchronization.

The Procedure Runs page now supports filtering jobs in the 'Waiting' status using the All Run Statuses filter.

The “All Projects” filter now includes plugin procedures, with a dedicated “Plugins” tab showing procedures. The Find, Search, and Custom Filter options now support filtering plugin procedures.

An Export as CSV button has been added to the Environment Inventory page, allowing users to easily export inventory data to a CSV file for reporting, analysis, or record-keeping purposes.

Pipeline tasks with automated retries now display the number of retries performed, whether the task completes successfully or reaches the maximum retry count.

Fixed modifyProcessDependency API to validate ACL configuration and return an error when required permissions are missing.

Widget table spacing added to properly wrap text. Text exceeding the 250-character limit now fully displays as hover text.

Fixed where task runs with pre-conditions showed incorrect durations in pipeline audit reports; task durations now display accurately for consistent reporting.

Agent installation can now be completed successfully with valid license usage.

Fixed overwrite mode handling when DSL statements invoke Groovy APIs; the mode is now safely ignored in these cases.

Event timings in Release calendar are now accurately reflected across “weekly” and “daily” views, ensuring better planning and visibility.

In Smart Deploy, manual tasks were not skipped during application deployments, causing property reference errors. Manual tasks are now correctly skipped after the first deployment.

Resolved issue where a missing subproject parameter during export caused import operations to assign incorrect procedures or applications to schedules.

The Pipeline runs page now allows the completion of manual tasks even when required parameters are set to their default values.

Fixed where importing EC-AnsibleTower configuration in YAML DSL would fail. The import process now works as expected, allowing successful configuration through YAML-based definitions.

Fixed API release deletion to prevent orphaned pipeline runs; running releases cannot be deleted.

Subfolders are now accessible as expected, ensuring consistent task configuration and execution in HA environments.

Resolved the issue of manual task approver assignees being incorrectly split when DSL expressions included commas.

In the Service Catalog, default values for catalog item parameters are now automatically populated using the "Dynamic Default Value" option. These values are based on dependencies defined in the "Default Value DSL" and are applied when parameter inputs are initially loaded during the catalog item execution.

When attempting to install CloudBees CD/RO inside a Docker container, the embedded web server may fail to start due to missing shared library dependencies. This issue is observed in Docker images based on certain Linux distributions, such as Ubuntu and Red Hat.<br/> <br/>

In recent CloudBees CI versions (verified with v2.452.4.1), if a CloudBees CI pipeline build triggered from CloudBees CD/RO is waiting for input and is aborted abruptly (for example, via jenkins-cli.jar or by aborting the CloudBees CD/RO pipeline), the approval details for that input step are not recorded in the CloudBees CI Build Audit Report.<br/> When approvals are approved or rejected through the CloudBees CI UI, the details are captured in the audit report as expected.

When running a pipeline with sub-pipelines, the progress percentage of the main pipeline does not update correctly when a sub-pipeline is restarted.

In the Pipeline Stats dashboard, if your query returns a pipeline with only a few runs, the widget labels on the X-axis may overlap in some cases, which may cause them to be unreadable. This is issue is fixed once a greater number of results are returned.

If upgrading from v2023.06.0 or earlier to v2023.10.0 or later, if Administration  Server settings &gt; UI settings &gt;Instance header is Enabled, and has a null value for the UI header label, the navigation may not load after an upgrade.<br/> +<br/>

On DevOps essentials  Platform Home page &gt; Administration &gt; Analytics server, the message WARNING: 'getDevOpsInsightServerConfiguration' API is deprecated. is displayed, because Elasticsearch is no longer supported. Additionally, it is no longer possible to configure CloudBees Analytics from this page, because it is deprecated and will be removed in a future release. <br/> +<br/> To configure your CloudBees Analytics server, navigate to Administration  Configuration &gt; Analytics server.

When updating from v10.2 or earlier to v10.3 or later, your upgrade may fail and break database consistency if legacy services or containers exist in your system. Additionally, even if the upgrade completes successfully with legacy services or containers present, it may still be impossible to run the validateDatabase API.<br/> +<br/> As a workaround, before upgrading from v10.2 and earlier, delete all legacy services and containers, and then perform the upgrade. When upgrading a clustered deployment of CloudBees CD/RO, before running the installer to upgrade, delete the contents inside the broker-data directory, located at <DATA_DIR>/broker-data-<hostname>.

You may experience SSO sign-in issues when using Kerberos due to a link:<a href="Microsoft known issue.

Mapping for microservices is not deleted when the source microservice contains fewer mappings than the target microservice. This mismatch of microservices occurs when the following actions are performed.<br/> <br/> On the DEV server:<br/> <br/>

Before upgrading from CloudBees CD/RO v10.2 and earlier, if legacy services exist in your system, upgrades may fail and database consistency may break. Additionally, even if the upgrade returns successfully, it may still be impossible to run the validateDatabase API. <br/>

Currently, if a formal parameter depends on a dropdown menu to get project parameter dependencies for object-like parameters, such as projectName, you can select multiple options in dropdown menus. However, there is only an object name (or list of names in case of multi-select) in the parameter value with no connection to a project and without the ability to identify which object exists in which projects. <br/> +<br/> CloudBees does not recommend using multi-select options for parameters used as project parameter dependencies for object-like parameters when configuring formal parameters. This applies to the following formal parameter types:<br/> +<br/>

In CloudBees CI job responses, actual parameters are returned that are not defined within the job. Additionally, saving and reloading the tasks doesn&#39;t clear undefined actual parameters.

On Windows agents, &quot;Export DSL&quot; catalog item fails to export objects that end in spaces.

When running getCIBuildLog for a CloudBees CI build, the build log cannot be accessed without restarting the build CloudBees CI controller. As a workaround, restart your CloudBees CI controller, and set up a number of executors, and getCIBuildLog can then be used to access the CloudBees CI build logs.

The flowRuntime response contains hasCIJobs=1 if a release was started from CloudBees CD/RO and the previous release run was triggered within CloudBees CI.

When a process step that is not manual is modified to be manual after the process runs, but before the associated job step evaluated, the step hangs and adds a java.lang.IllegalStateException: Unknown step type: manual exception to the log.

Events that originate from the default CloudBees CI create default configurations. URLs for these new controllers are not Jenkins-configured URLs and cause 401 errors.

When using PostgreSQL with change tracking enabled, EcAuditStrategy errors may appear in the server log. This is a known issue, but is not expected to have any effect on the performance of the system.

The CloudBees CD/RO UI does not allow you to transfer artifacts across zones.

&nbsp;When a custom data retention policy schedule is set to run once, the data is not purged after archiving. To purge data after archiving, use a repeat schedule or the global data retention setting.

The MeanLeadTime report does not work correctly when Elasticsearch only has pipeline runs but no release runs.

SyncArtifactVersions procedure completes with success, rather than showing a warning, when manifest is missing and overwrite = false.

When you use the Automation Platform UI to upload and publish artifact files with non-English characters in their file names, the operation fails with the following error: Upload file: Exit code 1: ERROR: Publish failure: Unexpected retrieval exception for repository error.

Modifications of LDAP user data (such as email addresses) on an Active Directory server after registration in CloudBees CD/RO do not appear properly in user details (in the Automation Platform UI, the Deploy UI, or ectool) until the CloudBees CD/RO server is restarted.

(Microsoft Windows platforms only) If the Elasticsearch cluster used by CloudBees Analytics is in the red state (meaning that it only partly functions and some data is unavailable), then upgrade, reconfigure, and uninstall operations will not work. Since the Elasticsearch service cannot be stopped when a cluster is in a red state, you must stop the Elasticsearch service process from the task manager before running the installer for these actions.

The Microsoft Edge® browser does not work with SAML 2.0 and is missing a self-signed certificate during redirection from the identity provider to the service provider. Microsoft Edge® is not recommended for sign-in via SAML 2.0.

The LANG environment variable must be set to en.US.UTF-8; otherwise, the upgrade fails. Refer to link:https://docs.cloudbees.com/d/kb-360046953992[KBEC-00452 - Error installing CloudBees CD/RO 10.0.x when the LANG environment variable is different than en.US.UTF-8 for details.

Error prompts for runtimes started by a schedule are not visible if the schedule was created with a missing configuration.

The stage inclusion status in the Release Dashboard changes color after a stage is renamed.

If an application process step cannot expand to its child steps (because of an invalid run condition or an invalid formal parameter), then the step is not retried even if it uses retry on error error handling. The job eventually completes with an error.

The retry count for group tasks or rules using automated retry on error is missing from the Pipeline runtime page.

Multiple mapped environments with the same name from different projects are not supported in email notifications.

A project import might not include the path-to-production view.

All subreleases of a release must appear before the release in the DSL for the release-to-subrelease links to be created.

The ability to search by assignee in a Deployment Report is not available in the CloudBees Analytics report editor.

If Release Command Center was set up for Jira for user stories and defects, and the JIRA project name was mapped to the release project name using the field mapping projectName:releaseProjectName, then before upgrading to 10.0, the field mapping must be updated to mention the actual release project name using the following field mapping format: "release-project-name-in-CloudBees CD/RO":releaseProjectName.

Approval by email on manual tasks should not expect parameters.

If you use the ectool export to export your system configuration from a previous release, and then use ectool import to import the same configuration to a CloudBees CD/RO 10.0 server, some out-of-the-box content introduced in the releases since the version from which the full export was done, such as new or updated plugins, new catalog items, and persona-based menu items, may be missing in the CloudBees CD/RO server UI. It is recommended to use ectool export and ectool import only between servers at the same version.

SSO does not work unless PHP configuration is changed due to a security-related request. As a workaround, change session.cookie_samesite to "Strict" in /opt/electriccloud/electriccommander/apache/conf/php.ini and restart the web server.

CloudBees CD/RO v10.1 introduced new triggers and an updated UI for them. Pre-v10.1 triggers will continue to work but there is no UI to review or run them.

Before using the export command to perform a full data export from the CloudBees CD/RO database, delete any legacy definitions and references to service objects from applications and releases.

You can only revert changes for high-level design objects such as applications procedures, procedure steps, workflow definitions, and state definitions.

Enabling Recursively Traverse Group Hierarchy might impact system performance when the LDAP group hierarchy is traversed. The amount of impact varies with the configurations of the CloudBees CD/RO and LDAP servers, the depth of group hierarchy in the LDAP server, and the network latency between the servers. Ensure that your directory provider can handle the additional load for supporting nested group hierarchy traversal.

System performance might decrease if you disable change tracking at the server level and then re-enable it. Change tracking is enabled by default. For details about using change tracking, refer to change tracking.