CloudBees CD/RO v2023.03.0

CloudBees is pleased to announce the v2023.03.0 long-term support (LTS) release of CloudBees CD/RO. With this release, CloudBees added several new features and system improvements, including:

  • Advanced microservices deployment strategies with Argo Rollouts

  • YAML DSL enhancements

  • Jenkins interactive input support

  • API changeOwner enhancement

  • Common tools archive for Linux distributions

  • Agent images with preinstalled tools

  • Proxy support for email configurations

  • EKS v1.25 support

  • Improved Kubernetes upgrade instructions

Refer to New features and Feature enhancements below for more information.

Security fixes

This release includes the following security updates to address potential vulnerabilities:
  • Apache web server is upgraded from 2.4.54 to 2.4.55. For details, refer to the Apache HTTP Server Project. [BEE-29816]

  • The Apache ZooKeeper server included in CloudBees CD/RO Docker images has been upgraded to v3.8.1. [BEE-17920]

  • Elasticsearch is upgraded to 7.17.9. [BEE-29817]

  • OpenSSL is upgraded from 1.1.1s to 1.1.1t.[BEE-29816]

  • PHP is upgraded from 8.1.14 to 8.1.16. For details, refer to the PHP 8.1.16 Release Announcement. [BEE-29816]

New features

Advanced microservices deployment strategies with Argo Rollouts

CloudBees has added the ability to use Argo Rollouts to provide advanced deployment capabilities, such as blue-green, canary, canary analysis, experimentation, and progressive delivery features to Kubernetes. To support this feature, the following changes were made:

Jenkins interactive input support

Allows for manual approval of a CloudBees CI build job in CloudBees CI from CloudBees CD/RO. If a CloudBees CI build job triggered by CloudBees CD/RO pauses waiting for user input, the CloudBees CI Input icon displays on the task. If you select this icon, the system takes you directly to the approval screen in CloudBees CI for you to approve. Once approved, the system returns to the build data window and displays the continuing pipeline run.

For more information, refer to Native CI integration.

Common tools archive for Linux distributions

As of release 2023.03.0, CloudBees CD/RO now includes an option to manually download and install a common tools archive for Linux distributions. This archive includes the following tools:

  • ectool

  • ecclientpreflight

  • ec-groovy

  • ec-perl

  • postp

This option may be helpful if you do not want to over-assign ROOT privileges to installers on your platform. For more information, refer to Install CloudBees Tools from archive.

Feature enhancements

CloudBees CD/RO agent images with preinstalled tools

Starting with CloudBees CD/RO 2023.03.0, agent images are available with the following preinstalled tools:

  • Helm v3.11.1

  • kubectl v1.26.1

  • kubectl-argo-rollouts v1.4.0

Enhanced changeOwner API

The --recursive argument of the changeOwner method has been enhanced to apply the ownership changes of pipelines, releases, and flowRuntime objects to associated child objects. When set to the default value of false, ownership changes are applied only to the selected object. If set to true, ownership modifications are applied as follows:

  • Pipeline and releases: Changes are applied to stages, gates, tasks, associated flow and flow state objects, and common objects. Common objects are properties, email notifiers, event subscriptions, and formal parameters.

  • flowRuntime: Changes are applied to flowRuntimeState, nested flowRuntime objects, and common objects. Common options are properties, email notifiers, event subscriptions.

YAML DSL enhancement

The DSL IDE was enhanced to display object hints. When you place your cursor on an object, such as Object ID, and enter the keyboard shortcut, a help window displays the object details.

For more information, refer to DSL editors.

Proxy support for email configurations

CloudBees CD/RO now supports proxies in email configurations. To add proxy configuration for SMTP traffic:

  • On traditional platforms, update your CloudBees CD/RO server wrapper.conf file with the following entries:





  • For Kubernetes installations, the following lines must be passed in the flow-server Helm chart as ecconfigure commands:

      ecconfigure: "<yourhost> \
        --wrapperJavaAdditional=10002=-Dmail.smtp.proxy.password=<yourpassword> \
        --wrapperJavaAdditional=10003=-Dmail.smtp.proxy.user=<youruser> \
Improved Kubernetes upgrade instructions

Improved instructions for upgrading from Kubernetes v1.21 and earlier to v1.22 or later. The instructions now include the required steps for disabling nginx-ingress and enabling ingress-nginx, as required by Kubernetes. For more information, refer to Upgrade CloudBees CD/RO on Kubernetes.

Performance improvements


Plugin enhancements

CloudBees CD/RO plugins catalog

The CloudBees CD/RO plugins catalog is available on the CloudBees CD/RO documentation site.

For more information about plugin support and versioning, refer to Plugin Concepts.

Legacy platform plugin manager deprecation

The plugin manager built into the legacy CloudBees CD/RO Automation Platform UI was deprecated with v2023.02.0. CloudBees strongly recommends that you migrate to the new plugin manager. For plugins that support the new plugin format, you can migrate legacy plugin configurations using a built-in Migrate configurations Service catalog item.

Migrating your custom plugins

To use the new plugin manager, your plugins must align with the CloudBees plugin development kit (PDK) configuration model and contain the plugin configuration as a first class object. To migrate an existing plugin to the new plugin manager/configuration, CloudBees recommends rebuilding your plugins using the PDK. For more information, refer to Migrate legacy plugins to pdk. Once a plugin is built to support the PDK configuration, legacy plugin configurations for the plugin may be migrated using a built-in Migrate configurations service catalog item.

Plugin configurations based on GWT may not be available to view in the new plugin manager. To view the plugin’s configurations, navigate to the Platform home page, then select the plugin project and choose the Properties tab. The <PluginName>_cfgs property contains the references for all configurations for the plugin. For more information, refer to Migrating your plugin configurations.

Plugins that will be migrated

The following CloudBees supported plugins are not configured with the new plugin configuration, but will be updated soon:

  • EC-MySQL

  • EC-Splunk

  • EC-Twistlock

Plugins that will be deprecated

The following CloudBees supported plugins do not support the new plugin configuration and will be deprecated and removed from the catalog:


  • ECSCM-Accurev

  • ECSCM-Bazaar

  • ECSCM-ClearCase


  • ECSCM-File

  • ECSCM-Git

  • ECSCM-Mercurial

  • ECSCM-Perforce

  • ECSCM-Property

  • ECSCM-Repo

  • ECSCM-StarTeam


  • ECSCM-Synergy


  • ECSCM-Vault

  • EC-Twitter

Plugins moving to the community

The following plugins will be removed from the plugin catalog and migrated to the community:

  • EC-Apache

  • EC-Azure

    CloudBees has released a new AzureCLI plugin to replace this plugin.

  • EC-AzureDevOps

    CloudBees has released a new AzureDevOps plugin to replace this plugin.

  • EC-BigIp

  • EC-DB2

  • EC-DBI

  • EC-EC2

  • EC-Gerrit

  • EC-Selenium

To generate a list of legacy plugin configurations on your system, you can use this DSL script.

Contact CloudBees Support if you require assistance updating these plugins to support the new configuration.

Plugin updates

EC-DslDeploy 4.1.9

Fixed regression with multiline property values generation.

EC-FeatureFlags 1.2.5

Updated third-party library dependencies.

EC-GCP-ComputeEngine 2.5.11

Fixed the null value in the ListInstances JSON output.

EC-Helm 1.7.0

Internal improvements for CloudBees CD/RO microservices deployment.

EC-Kubectl 1.3.0

Updated the logger.

EC-Selenium 2.0.10

Released to the community.

EC-SonarQube 2.1.3

Fixed an issue with the Ignore SSL errors option for the Get Last SonarQube Metrics and CollectReportingData REST-based procedures.

EC-SQLServer 3.0.0

The plugin has been migrated to the PDK framework, and now supports PDK model plugin configurations.

Upgraded from Perl 5.8 to Perl 5.32. The plugin is not backward-compatible with releases prior to CloudBees CD/RO 10.3. Starting with 3.0.0, a new agent is required to run the plugin procedures.

Trigger-Property 2.0.0

Upgraded from Perl 5.8 to Perl 5.32. The plugin is not backward-compatible with releases prior to CloudBees CD/RO 10.3. Starting with this release, a new agent is required to run the plugin procedures.

Plugin Development Kit enhancements


New platform support

This section lists new platform support.

EKS v1.25 support

As of v2023.03.0, CloudBees CD/RO has been tested on EKS v1.25 and is supported.

Refer to the following topics for a list of officially supported platforms for CloudBees CD/RO:

Resolved issues


When an artifact name and version are specified in a component with a property reference, the getPartialApplicationRevision() API returns and the UI displays the specific deployed name/version in the Create snapshot dialog.


Fixed an issue that caused an error when a pipeline manual task was saved without an approver.


Increased the CloudBees CD/RO web server memory limit from 100M to 250M to resolve an issue with DSL exports. To set the CloudBees CD/RO web server memory limit, use the ecconfigure --webPhpMemoryLimit Maximum amount of memory PHP script may consume option.


Fixed an issue that caused empty values in the Top 10 SCM Repositories with the most file changes report.


Updated the setDatabaseConfiguration API error message for databases that contain incorrect symbols to: [InvalidName]: 'databaseName' must be between 0 and 255 alphanumeric or '_' characters.


Unique constraints work on MySQL, MariaDB, and PostgreSQL databases when a release and a deployed application are located in the same project.


The getDeploymentHistoryItems API returns the latest deployment information for existing environment inventories.


The SeedInventory procedure no longer updates multiple resources for an environment when only one resource is specified.


Fixed a NPE in the archiving service that occurred when the archiveDirectory parameter was not specified.


Fixed an issue with restarting failed pipelines that caused unselected stages to restart.


Fixed an issue in v10.11 that prevented importing projects with custom properties using EC-DslDeploy.


Fixed an issue with the See more link on the pipeline Properties page in the UI.


Updated the default value of the Track changes to value property option to be false when enabling change tracking for a project.


Fixed an issue with CloudBees Analytics dashboard imports with the COMMANDER_CENTER type in the overwrite mode.


Fixed a StackOverflowError issue with masking secrets in logs.


Applied UriCompliance.LEGACY to the updated Jetty HTTP server for backward-compatibility with the previous version of Jetty server v.9.4. This change also adds supports for CloudBees CD/RO agents v10.5 and earlier with broken ec-groovy that do not use parameter URL encoding.

By default, the legacy mode is enabled in the CloudBees CD/RO server wrapper.conf configuration file:

If your platform contains ill-formed Groovy scripting and does not use URL encoding, it could be possible to exploit in unexpected ways.

To disable this option and configure your CloudBees CD/RO server to be more secure, use the following ecconfigure command: ecconfigure --serverSupportBrokenEcGroovy=false


seedEnvironmentInventory returns the last successful version for one particular resource if it was seeded only for one resource.


Fixed an issue in the getPipelineRuntimes REST API for EC-Groovy and Swagger. The getPipelineRuntimes REST API did not work when only the flowRuntimeId parameter was specified.


The getApplicationEnvironmentInventory API returns the last successfully deployed artifact version for a particular resource if a component was deployed on it.

Behavior changes


Installation notes

For complete installation and upgrade information, refer to CloudBees CD/RO on Kubernetes and Install CloudBees CD/RO on traditional platforms.

CloudBees deprecated the CloudBees CD/RO ec-jruby and ec-jython wrapper programs with v10.11. The wrapper programs are no longer installed as part of CloudBees CD/RO tools.
Potential backward incompatibility

CloudBees CD/RO Docker images are now based on UBI minimal instead of UBI standard, as in previous releases. Some packages are not installed on our Docker images by default. This may cause backward incompatibility if your environment depends on these tools and utilities. CloudBees CD/RO Docker images now use microdnf as a package manager and yum and dnf package managers are no longer available. To retain backward compatibility, CloudBees CD/RO provides a symlink for microdnf as dnf. These package managers are not 100% compatible, which may cause unexpected errors and require modification of the scripts.

CGI module and support removed

CloudBees removed the CGI module and support with v.2023.02.0. After you upgrade your CloudBees CD/RO server to v2023.02.0, you must also upgrade your CloudBees web server.

UI file upload limits are now controlled by PHP in /opt/cloudbees/sda/apache/conf/php.ini.

For default parameter values and more information, refer to Configuration settings preserved after an upgrade.

Duplicate applications warning

CloudBees CD/RO v10.9 included a fix for an issue that caused duplicate applications for applications created in the UI. The upgrade process fails when there are duplicate applications. CloudBees resolved this issue for MariaDB, MySQL, and Postgres databases. Ensure that your current installation does not contain applications with duplicate names. You can rename or delete the applications. You must remove duplicate applications by ID using the deleteObjects API. You cannot delete duplicate applications by name. For more details and scripts to assist with this process, refer to KBEC-00513 - How to resolve applications with duplicate names before upgrading from a version prior to v10.9.

Apache ZooKeeper required update

The ZooKeeper version bundled with CloudBees CD/RO v10.5 was updated from v3.4.6 to v3.8.0. CloudBees CD/RO v10.5+ requires ZooKeeper v3.8.0. For installation and upgrade instructions, refer to Install ZooKeeper and Upgrade a clustered environment.

Legacy services applications and container entities

In CloudBees CD/RO v10.3, the legacy Services applications and Traditional applications with containers were deprecated and removed. Before you upgrade to CloudBees CD/RO v10.3 or later, you must migrate your applications to the current microservices application model.

Also, before upgrading from CloudBees CD/RO v10.2 or earlier you must delete all legacy services and containers. This will prevent upgrade failure, a database consistency break or inability to run the validateDatabase API.

Legacy webhook triggers

As of v10.8, webhook triggers configured and scheduled before v10.1 have been deleted. Polling triggers configured and scheduled prior to v10.1 continue to work, but they are not available from the UI to review or run.

CloudBees CD/RO server installation binaries are signed for traditional installations so that you can verify their origin and authenticity. Verifying binaries is an optional step in the installation process than can help ensure you are not the victim of a man-in-the-middle attack. For more information, refer to Verify installation binaries.

CloudBees CD/RO on Kubernetes

Sample CloudBees CD/RO server and agent Helm chart values provide the CloudBees default installation values. The CloudBees CD/RO images.tag value associated with v2023.03.0 is 2023.03.0.161439_3.2.38_20230307.

Starting with 2023.03.0, CloudBees introduced the ability to add additional environmental variables for Kubernetes CloudBees CD/RO agents. You can add environmental variables in the cloudbees-flow-agent Helm chart using the entry for extraEnvs.

CloudBees CD/RO Docker images and Helm charts are signed so that you can verify their origin and authenticity. Verifying Docker tags and Helm charts is an optional step in the installation process than can help ensure you are not the victim of a man-in-the-middle attack. For more information, refer to Verify Docker images and Verify Helm charts.

CloudBees CD/RO v2023.03.0 now supports Kubernetes v1.25. As a result, Kubernetes PSP support is now deprecated in CloudBees CD/RO 2023.03.0 Helm charts.

CloudBees CD/RO Universal Base Image (UBI)

The actual UBI associated with v2023.03.0 is 9.1.0-1760.1675784957.

Upgrading gateway agents

All gateway agents that meet the following criteria must be updated to CloudBees CD/RO v10.2+:

  • Your enterprise implements a multi-zone environment.

  • Agent versions are a combination of pre-v10.2 and v10.2+.

  • The access route to a v10.2+ agent is configured through a pre-v10.2 gateway agent.

Configuring autostart services for Linux installations

Linux installations that you perform as a non-root user or without sudo permissions cannot automatically start the CloudBees CD/RO server, web server, repository server, or agents. Instead, you must set up service autostart after installation is complete. Refer to Configure autostart for non-root/non-sudo Linux installations to learn more.

Upgrading your CloudBees CD/RO environment
Before starting an upgrade, make sure to back up your existing CloudBees CD/RO data.
Upgradable versions

Upgrades to CloudBees CD/RO 10.x are supported only from ElectricCommander 5.0. For upgrade instructions, refer to the Upgrade on traditional platforms.

Updating the MySQL configuration before upgrading

Since release 8.0.1, CloudBees has instructed customers using a MySQL database to add the following two lines to their MySQL configuration:

init_connect='SET collation_connection = utf8_unicode_ci, NAMES utf8'

Before upgrading CloudBees CD/RO, you must remove these lines or comment them out. Otherwise, jobs will not start.

Ensuring the correct default MySQL default collation

Make sure that the default collation for the MySQL database schema is set to utf8_unicode_ci or utf8_general_ci and that no table in the schema overrides this. The CloudBees CD/RO server checks this configuration on startup and logs errors in the server log if it is not set correctly.

If the collation is not configured correctly, entering non-ASCII text into CloudBees CD/RO can cause errors. For example, setting a release name to a non-ASCII value, and attempting a search, causes an exception.

If your MySQL database schema, or any tables within, are set to a non-UTF-8 collation order, refer to the Knowledge Base article KBEC-00385 - Converting a MySQL Database From Latin-1 to UTF-8 for detailed instructions about safely converting your schema to UTF-8. [NMB-26521, NMB-27459]

Upgrading agents that run the ec-groovy job step in multizone deployments

In multizone CloudBees CD/RO deployments, CloudBees CD/RO agents that are in a different zone than the CloudBees CD/RO server must be upgraded to version 9.0 or later for the ec-groovy job step to run successfully on those agents. You must also upgrade the gateway agents that lead back to the server’s zone, including those in any zones in between the agent’s zone and the server’s zone. [NMB-27490]

For details about multiple zones and gateway agents, refer to Zones and gateways.

Removing the SSL 2.0 Client Hello or SSLv2Hello protocol from your security configurations

CloudBees recommends removing the SSL 2.0 Client Hello or SSLv2Hello protocol from your security configurations for all components. [NMB-27934, NMB-29326]

  1. Upgrade agents to the latest operating system version for security reasons.

  2. If this warning appears on the Automation Platform UI:

    Note: We recommend removing `SSL 2.0 Client Hello` format from server configuration and upgrade older agents as indicated on the Cloud/Resources Page to avoid security risk.

    then enter the following command on the CloudBees CD/RO server:

    $ ecconfigure --serverTLSEnabledProtocol=TLSv1.2
Upgrading the CloudBees Analytics server

This section provides information about upgrading the CloudBees Analytics server.

Potential breaking change: Elasticsearch update

The Elasticsearch version shipped with CloudBees Analytics v10.2 has been updated from v6.6.2 to v7.10.2. As such, this update may create breaking changes in your custom reports. All changes related to the new version are described in Elasticsearch documentation. The following change may affect your reports the most. [BEE-2717] * Accessing missing document values throws an error. The doc['field'].value throws an exception if the document is missing a value for the field field.

To check if a document is missing a value, you can use doc['field'].size() == 0.

  • It is not possible to upgrade CloudBees Analytics v9.0.1 and below to CloudBees Analytics v10.2.0 and above. The installer exits with an error and an appropriate message when such an update is attempted. If you need to upgrade CloudBees Analytics v9.0.1 and below, you must first upgrade to a version between 9.1.0 and 10.1.0, or 9.0.2 and above. After that, you can upgrade CloudBees Analytics to v10.3.0 or higher. [NMB-31030]

  • For previous CloudBees Analytics upgrades from v9.0.1 and below: CloudBees Analytics data may contain obsolete indexes that are incompatible with CloudBees Analytics v10.2.0 and above. To work correctly, it is necessary to re-index these indexes before an upgrade. The installer prompts you to do this before upgrading.

    • In console mode and UI mode, the installer displays the following prompt if outdated indexes are detected:

      One or more Elasticsearch indexes were created in an obsolete version of Elasticsearch.
      These indexes must be re-indexed for the upgrade to be successful.
      Do you want to start the reindexation? [n/Y]

      After an affirmative answer, the installer automatically re-indexes and continues the upgrade.

    • In silent mode, the installer reindexes automatically.

  • Backing up and restoring custom settings

    The CloudBees Analytics installer overwrites the elasticsearch.yml configuration file with a new file. This file includes a Custom Settings section, which lets you add Elasticsearch settings not managed by the CloudBees Analytics server without being lost during an upgrade. The installer preserves the settings in the Custom Settings section. [NMB-25850]

  • Upgrading CloudBees Analytics clusters

    The principle of forming a cluster in CloudBees Analytics has changed in v10.2 due to the update of Elasticsearch v7.10.2. In this regard, an additional action is required to upgrade to CloudBees Analytics v10.2 or later:

    When updating the first master node, you must explicitly specify that it is the first node to be updated. If this action is not performed, any cluster that is being updated is placed out of service.

    All installers have been instrumented to accommodate this change. Refer to Upgrade the CloudBees Analytics server for more details. [BEE-2717]

  • CloudBees Analytics server configuration notes

    For a production environment, CloudBees recommends that you install the CloudBees Analytics server on a system separate from systems running other CloudBees CD/RO components (such as the CloudBees CD/RO server, web server, repository server, or agent). If you must install it on the same system (such as for testing or other non-production or trial-basis situations), refer to CloudBees Analytics server with other components for details.

    If your CloudBees Analytics server is configured with multiple nodes in a Kubernetes environment, you must pre-generate your certificates. For more information, refer to Install CloudBees CD/RO within Kubernetes.
CloudBees CI operations center configurations

After upgrading to CloudBees CD/RO v10.7 from v10.0.x, you may need to rework your CloudBees CI operations center configurations. * In v10.0.x, CloudBees CI operations center URLs specified in configurations are silently appended at runtime with the /cjoc path component. * In v10.1, URLs are used as defined in configurations. The /cjoc component is not appended. To maintain pre-v10.1 runtime compatibility, the v10.1 upgrade process modifies CloudBees CI operations center URLs in existing configurations by hardcoding the /cjoc path component. You need to rework existing URLs in configurations where appending the /cjoc path component is inappropriate.

Configuration notes

Performing a full import

During a full import, the import operation might hang in the following scenarios. To import successfully into CloudBees CD/RO 8.0 and newer versions, perform the appropriate workarounds [CEV-15447, CEV-11873]:

  • A manual process step in a process has formal parameters. The workaround is to remove the entry related to the property sheet for the job step that is associated with the manual process step.

  • In the exported XML file from an earlier release, two pipelines are in different projects, and both pipelines have no gate tasks. The flow associated with the pipeline is duplicated under both projects. The workaround is to remove the flow element under the projects.


When an application is cloned from one project (the original project) to another (the destination project), the tier maps for the application point to the environments with the same names in the destination project. To deploy the application to the environments in the original project, you must first create tier maps connecting the application to those environments.

Known issues


With CloudBees CD/RO v10.2.1 and earlier, the DSL Import service catalog fails for grouped tasks.


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


The UI does not allow the transfer of artifacts across zones.


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.


When you save DSL for a dropdown menu, the code is evaluated to catch syntax errors. This evaluation is not the same as when the parameter is used. This can result in a property reference error because the properties may only be available when the parameter values are set. A workaround is to use a try-catch statement where the property path is a property that is not available in the definition context:

def value
try {
  value = getProperty(propertyName: 'property path').value
} catch (e) {
  return []


CloudBees CI job tasks with a $[] branchName in the definition fail.


When using Postgres with change tracking enabled, EcAuditStrategy errors may appear in the server log. This is a known issue, but is not expected to affect system performance.


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.


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


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.


When upgrading to CloudBees CD/RO 10.6 (Helm chart version 2.16.0) from previous versions, the flow-web pod fails to start, with the message: ERROR: Error when opening "<path-to-commander>/commander/config.php.temp": Permission denied

As a workaround, in your flow-web Helm chart:

  1. Find the entry for web.ecconfigure.

  2. Delete the value "--webDefaultUI commander".

  3. Restart the upgrade.


When you restart a running pipeline with an active CloudBees CI job task, the task is aborted with force=true, as a result, the CloudBees CI job is not aborted. If the CloudBees CI job is waiting for interactive input and does not have a timeout configured, it continues to wait for input. When you review CloudBees CI job details, CloudBees CD/RO does not show that the job is waiting for input because CloudBees CI jobs are not examined for completed tasks.


Browser redirects to port 2080 during first navigation to CloudBees CD/RO deployed from CloudBees Software Delivery Automation and Flow Helm charts.


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


When an application with snapshots created in CloudBees CD/RO 6.1 or earlier is cloned and a project containing this application is imported to CloudBees CD/RO 6.3 or higher, the import operation fails.


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.


No error prompt appears for failed tasks and retry tasks during a pipeline runtime.


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.


Jobs might not appear upon drill-down into the "Clusters With Most Deployments" widget in the CloudBees Analytics Microservices Dashboard if the service does not contain a deploy step in the process.


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

CEV-19239 CEV-19259

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. 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 revert changes only for high-level design objects such as applications procedures, procedure steps, workflow definitions, and state definitions.

Restarting the CloudBees CD/RO server while new records are created for all tracked objects might take at least as long as an export or import of all projects (10 to 40 minutes for a large project).


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