CloudBees CD/RO v2025.06.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.

For Kubernetes environments, a new Custom Autoscaling feature has been introduced to automatically scale CloudBees CD/RO build resources based on your environmental load. Using this feature allows build resources to automatically be scaled up and down in configured resource pools.

You can now configure email notifications for task events, such as start, complete, failure, and abort, within the task options menu in the Notifications tab for given recipients, such as users and groups. Additionally, the default notification email includes event details, such as pipeline, stage and task name and a link to help you quickly navigate to the pipeline run details page.

You can now access and integrate CloudBees CD/RO JAR libraries through the cloudbees-cdro-maven-public-releases, which simplifies dependency management and development workflows. The API bindings for the ElectricFlow Java/Groovy library were published to CloudBees CD/RO. This enables you to use Maven or Gradle to add it as a dependency directly, eliminating the need to upload the library to your own Maven servers.

CloudBees CD/RO has been tested using Kubernetes v1.32 and is supported for Azure Kubernetes Service (AKS), Amazon Elastic Kubernetes Service (EKS), and Google Kubernetes Engine (GKE). For more information, refer to Supported platforms for CloudBees CD/RO on Kubernetes.

On the Pipeline runs page, run details now render dynamically based on your browser window size. To improve usability, vertical scrolling has been refactored to scroll through the entire pipeline, rather than being limited to individual stages. Additionally, when selecting a deployer task within a stage, the Deployer window opens at the same location.

Retrieving and rendering data on the Releases and Pipeline runs pages has been improved to reduce load times and enhance usability. These improvements include:

The search field now dynamically displays results as you type, leveraging names to find relevant entries. Any search that requests a specific detail will return all results that match the entered name.

CloudBees CD/RO has been tested using Windows Server 2022 and is fully supported. For more information, refer to Supported platforms for CloudBees CD/RO on traditional platforms.

The Environment Inventory page now applies dynamic searching, enabling real-time filtering of results as you type. Combined with enhanced filter capabilities, multiple filters can now be applied simultaneously to experience faster, more accurate search results across your environment data. The Environment Inventory page also supports drag-and-drop functionality, allowing you to reorder the environment columns for a more personalized view.

The following Commander UI pages have been updated to use the Flow UI:

CloudBees CD/RO has been tested using PostgreSQL 17 and is fully supported. For more information, refer to Supported platforms for CloudBees CD/RO on traditional platforms.

You can now navigate the full list of results in a data retention policy summary and previews using the bottom-right page navigation.

By default, the values file located in the same directory path as the microservice Helm chart is used. An option has been added to use an alternate values file located in another directory when configuring the microservice.

Data retention policy previews now display the number of objects potentially affected by the policy definition.

The run summaries for data retention policies have been improved to include specific information about the number of entries that were affected by the job.

Resolved an issue for CloudBees CI integrations that prevented triggering Multibranch Pipeline jobs when using newer versions of CloudBees CI (verified with v2.504.2.5). With this fix, CloudBees CD/RO pipeline tasks now successfully trigger CloudBees CI jobs and complete as expected.

An issue was reported where the emailEvent parameter did not accept multiple parameters when using ectool. This issue has been fixed, and now, the emailEvent parameter accepts multiple parameters as expected.

On Windows, an issue that caused manual plugin installations to fail with a No such file or directory error has been fixed. The installation logic has been updated to ensure compatibility with both Windows and Linux paths.

An issue was reported, where when running pipelines with manual tasks with smart deploy enabled, manual tasks were not confirmed as expected if the version of the release changed. This issue has been fixed, and smart deploy confirms manual tasks as expected, regardless of version number changes.

Fixed an issue where the Java JAR tool would throw a ClassNotFoundException because the Bouncy Castle dependency path was missing. Now, the dependency should be automatically resolved.

Fixed an issue in the EC-Rest plugin v2.5.7 where URL paths were incorrectly encoded.

When trying to create a microservice using ec-groovy, the createMicroservice API failed, and returned an invalid InvalidName error. This issue has now been fixed, and using ec-groovy with createMicroservice works as expected.

Fixed an issue where editing a procedure step with an attached credential parameter would return an error for the credential, even if the parameter was not modified.

In v2025.03.0, credentials attached to a procedure using Credential type > Attach and in the same project as the procedure were deleted when viewing or updating a procedure and selecting Save. This issue has now been fixed in v2025.03.1, and these types of credentials are no longer deleted from the procedure.

Due to potential security issues, CloudBees has migrated the archive for the ec-specs JAR to its own dedicated archive repository. If you receive a [ERROR] 503 Service Temporarily Unavailable message, you must update the ec-specs-examples Git repository and recompile your tests.

Fixed an issue where, when a pipeline or release run was archived through a data retention policy, the archive file did not include the properties associated with the run. Now, the run properties are exported to the archive file as expected.

When checking the credentials reference for an object, only the first 20 credentials displayed. This issue has been fixed, and now, all credentials for the object display as expected.

An issue causing SSL protocol failures (e.g., SSL upgrade failed: SSL connect attempt failed error:0A000410:SSL routines::sslv3 alert handshake failure) has been fixed in the product code. This eliminates the need to apply the manual workarounds previously required.

When selecting or deselecting projects in the filter, caused the total count to display incorrect values or reset when scrolling. The project count now accurately reflects the selected projects and remains consistent while scrolling.

Fixed an issue where duplicate ACL entries caused the Background Deleter to fail and prevented project deletion.

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

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 CloudBees CD/RO UI does not allow you to transfer artifacts across zones.

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.

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 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.

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 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.

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

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

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.

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

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.

You may experience SSO sign-in issues when using Kerberos due to a Microsoft known issue.

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.

On DevOps essentials  Platform Home page  Administration  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.

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

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.

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

Scrolling inside the Stage Summary or Deployer modal can unexpectedly close it, but this only happens when the content is scrollable.

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 KBEC-00452 - Error installing CloudBees CD/RO 10.0.x when 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.