Software Delivery Automation CD/RO v10.2

CloudBees is pleased to announce the CloudBees CD/RO 10.2 LTS release of the Software Delivery Automation platform. In 10.1, CloudBees introduced Software Delivery Automation connecting, automating, and orchestrating the software delivery process, by bringing together CloudBees CI and CloudBees CD/RO in a single platform. With this new release, CloudBees continues on the path to unified administration, data, and reporting. This release introduces new value across CloudBees CI and CloudBees CD/RO with:

  • Unified authentication across the platform.

  • New CI pipeline audit reports.

  • Improvements to microservices deployment modeling, and much more.

Security fixes

This release includes the following security updates
  • PHP is upgraded from 7.4.13 to 7.4.16. For details, refer to [BEE-3557]

  • OpenSSL is upgraded from 1.1.1i to 1.1.1k. [BEE-3557]

  • Apache web server: no changes.

New features

A Continuous Integration build audit report capability has been added to CloudBees CD/RO and CloudBees Analytics

A Continuous Integration build audit report capability has been added to CloudBees CD/RO and CloudBees Analytics to generate real-time reports of build events captured during the run of a given build or pipeline and is done in a systematic and scalable manner. This report offers the shared services owners and administrators a way to provide auditors with a comprehensive view of the pipeline audit trail in a time-saving, automated manner, thus reducing manual effort and error. The build events help trace:

  • Approvals and approvers

  • Test results

  • Generated artifacts

  • Source control activity

Microservices modeling
  • Rollback support has been added: New Enable automatic rollback on failure check box on Microservice Details UI is now available.

REST API available for License Usage Reports

The license usage reports, licenseReport and userReport, provide visibility into an organization’s CloudBees CI usage to ensure it is compliant with its license entitlements. These reports provide an accurate list of unique CloudBees CI users across all their controllers during a time period. If you use CloudBees Software Delivery Automation, you no longer need to use the User Activity Monitoring Plugin to track user activity.

You can try out these reports via the REST API endpoint.

For more information, refer to 10.2@cloudbees-cd-api:flow-api:apireport.adoc.

Feature enhancements

Sorting and pagination for Workload Insights

Previously, all reports were sorted by deviation. Now, you can use the up/down arrows to sort data by any of the numeric and boolean columns, such as max queue or build duration.

New pagination buttons enable you to view additional pages of data.

For more information, refer to CI Workload Insights.

Updated functionality in the Plugin Usage Report

You can now search by plugin name.

You can click a donut graph to drill-down into the corresponding plugins based on their status, for example unused or unsupported plugins.

For more information, refer to CI plugin usage.

Updated data retention property for the CloudBees Unified Data plugin

If CloudBees CI cannot send an event to CloudBees CD/RO, for example due to a network issue, it continues to attempt to send the event periodically. Previously, it attempted to send data for 24 hours. Now, it attempts to send data for up to 7 days. If the plugin cannot upload an event after 7 days, the plugin clears out the event queue and stops sending events until CloudBees CI is restarted or event collection is manually enabled again.

Redesigned single sign on experience
  • The SSO configuration has been revamped and simplified for both SAML and Kerberos, all from a single UI. The new UI is available here: from the main menu select Administration  Configurations  SSO configurations.

  • There is no longer a requirement to configure a directory provider (LDAP/AD) in the CloudBees Software Delivery Automation server when SSO is enabled.

  • The Deploy Kerberos keytabs option is deprecated from the Kerberos single sign on configuration UI. Installing keytabs is a one time IT admin activity that admins do by directly making the necessary configurations changes on the required servers and, therefore, not needed in the UI. [BEE-3298]

  • Documentation:

MySQL JDBC driver update

Mysql recommends using MySQL Connector/J 8.0 for use with MySQL Server 8.0, 5.7, and 5.6. CloudBees CD/RO is officially stopping support for MySQL Connector/J 5.* and will be supporting MySQL Connector/J 8. MySQL Connector/J 8.0 is highly recommended for use with MySQL Server 8.0, 5.7, and 5.6. Please upgrade to MySQL Connector/J 8.0. [NMB-29505]

The last few versions of the connector (v8.0.21 is the latest as of writing) has a bug so users should use version 8.0.16 until the bug ( is fixed.
Installer download page

CloudBees CD/RO installers are now available from the CloudBees download site via

Documentation enhancements
  • The complete set of CloudBees CD/RO server settings are now fully documented here.

Database support

No changes.

Browser support

No changes.

Performance improvements

Pipeline Runs and Release List UI

The UI response time when navigating to Pipeline Runs and Release List pages has been significantly improved, depending on the server configuration, when compared with previous releases.


The response times for the following APIs have improved significantly:

  • getReleases [CEV-23959]

  • getPipelineRuntimes [CEV-23712, CEV-24201]

Plugin enhancements

CloudBees CD/RO plugin catalog

The CloudBees CD/RO plugin catalog is available on the main product documentation site.

Updated plugins

The following is a list of key changes made to existing plugins. For a complete list, refer to Bundled plugin report


  • "Remote Copy - Native" fails because of PropertyReferenceError.


  • Implement default credential (instance-provided metadata) support in GCP Plugin.

  • Remove blocking ACL for Everyone group for plugins with Run Script procedure.


  • Procedure Collect Reporting Data commits with GCli library incorrectly parses commit messages.


  • Rollback feature support was added.


  • Add support for enabling EC-Kubectl to show up as a container plugin in the cluster definition.


  • Resolved`ectool runProcedure --procedureName CreateConfiguration` failure.


  • Plugin security fixes.

Flow PDK


  • Add new procedures with more than one step to PDK.

New platform support

This section lists new platform support. For the current list of supported platforms, consult Supported platforms for CloudBees CD/RO

Server support


  • Windows Server 2008 R2, 2012

  • Ubuntu 10.04, 12.04, and 14.04

  • Red Hat 5, 6

Agent support


  • Ubuntu 10.04, 12.04, and 14.04

  • Red Hat 5, 6

  • SUSE Linux enterprise server 10.3, 10.4, and 11.4

CloudBees CD/RO on Kubernetes
  • Red Hat OpenShift v4.5 and higher has been added.

  • Helm 2 support has been retired.

Resolved issues


Published a Helm chart update (version 2.10.1) to resolve an issue running CloudBees CD/RO charts on the new Amazon EFS Container Storage Interface driver.


Deleting of multiple releases with data sources causes lock leaks and threads deadlocks.


All jobs hanging on waiting for resource because scheduleStepsTrigger0 run into java.lang.NullPointerException in processResourceAndPoolTag.


Problem resolved where ./ectool pruneChangeHistory --daysToKeep 7 returns an Unable to prune the change history error when used with MySQL 8.


When using 10.1+ agents as gateway agents, the Server IP address server property has to be set.


DSL generated on ordered, non-alphabetized parameters results in error upon evaluation.


Benchmark CloudBees CD/RO Pipeline & Release performance /scalability with MySQL and MS-SQL with 10.2.


SSO via the CloudBees CD/RO application link in Okta dashboard does not work because immediately after login request there is an additional <logout/> request sent by browser.


Data Management does not work as expected.


[EC-DSLDeploy] Why EC-DslDeploy- becomes the owner of CloudBees CD/RO objects with Import DSL service catalog function.


Incorrect IDP SAML SSO configuration causes SAMLResponse with no NameId in the Subject section . When CloudBees CD/RO Server processes this response it fails with a NullPointerException.


Use of transaction block to runProcedure in a Service Catalog context does not work and fails with NPTR in CloudBees CD/RO 10.1.


[SDA] Main menu links not working as expected when opened in a new browser tab or window.


The permission of the job folders in workspace is drwxrwxrwx.


Security bug in JsonHttpDataManager.php ( when enabling config[traceRequests]) and improvements to JsonHttpDataManager.php and XmlHttpDataManager.php to debug webserver to CloudBees CD/RO Server connectivity issues during a JMeter load test.


The DSL getAccessTokens API returns a token but it cannot fetch the fields inside the token via dot notation in dsl.


Increase the default value for Maximum upload size property in the CloudBees CD/RO Server settings to at least the CloudBees CD/RO agent installer file size.


cd chart myql externalUrl does not work with clusteredMode.


[10.0.1] Windows installer fails in ecconfigure step when JAVA_TOOL_OPTIONS is set. Fix installer so it does not fail when JAVA_TOOL_OPTIONS in env during CloudBees CD/RO 10.0.1 and 10.1 install. Still -Duser.timezone should be set after install.


Allow the agent hostname to be configurable in the agent helm chart.


Add fallback logic in client-side perl specifically in waitForJob in connection through STOMP is not possible.


UI - [Cyberark CCP] Render the new testSecret field for CyberArk CCP credential provider type.


[HSBC] Add Existing PV support to the product helm chart.


SAML credential wasn’t converted at time of upgrade to cd v10.0.


PW01 jobs not processing after 3.4 million deferred messages on Feb15 & splitbrain in jgroups channels. Message Backlog started on Feb9 as jobs stuck after backgroundDelete deletes session in use by recheckSubscriptions. NMB-30194 exists but not an issue.


DB Sizing estimate section needs to be updated with sizing estimate for pipelines ( and releases).


Update liquibase to be compatible with latest MySQL JDBC connector.


Error in generated DSL if option parameters i.e formalParameter contains single quote char.


Document Configuring Directory Provider as a prerequisite for CloudBees CD/RO SAML authentication.


[Cyberark CCP] Connection tests are not correct.

NMB-30089, NMB-30565

During CloudBees CD/RO startup, when using MySQL with default Latin collation that is not supported, it logs a wrong KB link. utf8_general_ci to match the CloudBees CD/RO Docs.


CloudBees CD/RO UI My Work auto-refresh for user in 1400 groups (AD or local does not matter) generates a huge DB query for runIdQueryWithAclCaching that slows all other DB queries, which causes long CloudBees CD/RO Server restart.


QC: CloudBees CD/RO 10.x should support SQL Server 2019 support. Currently it is not supported for 10.0.2.


Job step waiting for resource on mac catalina as agent was unable to create directory on mounted workspace folder.


The createRelease and startRelease commands run from EC-Core runCommand in a pipeline task close the context that the release pipeline was created and started by the user who ran the parent pipeline. Instead, release pipeline is now owned by the parent pipeline project.


Remove requirement for pinging each gateway agent behind a load balancer in an HA setup for gateways.


PHP Deprecated: Array and string offset access syntax with curly braces is deprecated notices in apache error.log after upgrade to PHP v7.4.6.


Separate Other Deployment Tags from Deploy Deployments in Application Deployments dashboard.


Notifier templates have http:// for their URL. It may not work when using loadbalancer for the webservers. Provide ability to send notifier emails with http or https links in them


Move configuration variables outside of ecconfigure script due to security reasons.


Parameters disappear from dialog box in sub procedure.


Fix the SearchGuard permissions for scroll. Multiple hours delay from exponential backoff when processing sendReportingData requests that fail with HTTP 400 errors in updating pipeline tags.


Running pipelines is offering the already run tasks detail as link but not redirecting to any url.


ec_environment_variables property sheet is hidden under resources.


When using post gates with a parallel group of manual tasks, only the first manual task can be completed from UI. The UI displays You are not authorized to respond for remaining tasks and they cannot be completed.


Confirm pipeline ACL validations and manual task option use approver’s permissions for further pipeline execution.


Formatting of Automated Retry on Error needs review.


Small formatting issue on Component Process Step.


The tooltip for Suppress defaults in DSL Export is misleading. Fix tooltip so its purpose is understood.


The disabled Enable Change Tracking property is not taken into account in project DSL export.


Helm upgrade does not work. Init Job does not get deleted by itself at times and upgrade fails.


Nginx tcp port has a limit of 5 ports in GKE.


When using nested pipelines the dependent POST gate task/rule that has a wait dependency is starting before the dependee stage/task in the nested pipeline can complete.


The 'getReleases' command takes too long.


User should not have to refocus the search input each time new search result is loaded.


Response time is more than two seconds more for the request getPipelineRuntimes with maxResults:100 than with maxResults:250.


FlowRuntime properties doesn’t work on precondition.

Behavior changes

No changes.

Installation notes

For complete installation and upgrade information, refer to CloudBees CD/RO installation guide.

Legacy services applications and container entities

The legacy Services applications and Traditional applications with containers have been deprecated in this version of CloudBees CD/RO. We recommend upgrading your applications to the current microservices application model.

CloudBees CD/RO on Kubernetes

Sample CloudBees CD/RO server and agent Helm chart values, found here, provide CloudBees’s default installation values. The CloudBees CD/RO images.tag value associated with version 10.2 is

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. This means that you must set up service autostart after installation is complete. Learn more here.

Upgrading your CloudBees CD/RO environment

IMPORTANT: 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 Upgrade on traditional platforms.

Upgrading an older CloudBees Analytics version

Upgrading from a CloudBees CD/RO version 9.0.x , or earlier, requires upgrading the CloudBees Analytics server to 10.2. Upgrading from CloudBees CD/RO version 9.1, or later, does not require CloudBees Analytics server to be updated.

Updating elements containing applicationServiceMapping [CEV-16237 and CEV-16158]

If your XML export file from CloudBees CD/RO 8.0.1 or earlier versions has elements containing applicationServiceMapping, you must change all instances of that string in the file to serviceClusterMapping before importing the file into version 10.2. For example, change the following XML:



Backing up and restoring custom settings

The CloudBees Analytics installer overwrites the elasticsearch.yml configuration file with a new file. As of CloudBees Analytics version 8.3, the 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. If you added settings to this file in version 8.2 or earlier that you want to preserve, you must back up the file to a separate location before upgrading to version 9.2 or newer versions and then add the settings to the Custom Settings section after the upgrade. During future upgrades, the installer will preserve the settings in the Custom Settings section. [NMB-25850]

Updating the MySQL configuration before upgrading

Since release 8.0.1, CloudBees has instructed customers using a MySQL database to use the following two lines in 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

Since release 8.0.1, CloudBees has instructed customers using a MySQL database to ensure that the default collation for their database schema is set to utf8_unicode_ci or utf8_general_ci and that no table in their schema overrides this. As of release 9.0, 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, then entering non-ASCII text into CloudBees CD/RO might 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 in it are set to a non-UTF-8 collation order, refer to 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 older that fall into this category for security reasons:

    • Windows, Linux: 6.0.3 or older; 6.2 or older

    • Mac OS: 8.4 or older

  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 from Version 7.3 to Version 10.2.

Potential breaking change: Elasticsearch update

The Elasticsearch version shipped with CloudBees Analytics version 10.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 effect 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.

Upgrading CloudBees Analytics clusters in CloudBees CD/RO 10.2

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, the user must explicitly specify that it is the first node to be updated. If this action is not performed, a cluster being updated is placed out of service.

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

Re-Specifying configuration settings

The installers (GUI, interactive console, and silent mode) for the CloudBees Analytics server do not preserve the configuration setting for the CloudBees Analytics server host name ( --hostName ) or the setting for the Elasticsearch number of shards ( --elasticsearchNumberOfShards ) during the upgrade from 7.3 to 9.2. If you specified non-default values during the 7.3 Reporting server installation, you must re-specify these settings during the upgrade. (All other settings are preserved.)

CloudBees Analytics server configuration notes

For a production environment, CloudBees recommends that you install the CloudBees Analytics server on a system other than 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.

CloudBees CI operations center configurations

After upgrading to CloudBees CD/RO v10.2 from v10.0.x, your CloudBees CI operations center configurations may need to be reworked.

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

In order 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 the 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 create tier maps connecting the application to those environments.

Known issues


In the CloudBees CD/RO and CloudBees Analytics Continuous Integration Builds screen, if a build has a Running status, the Project column may temporarily not display project information. Once the build has completed, the Project column correctly displays the project information for each build.


Browser redirects to port 2080 during first navigation to CD deployed from SDA and Flow Helmm 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.


(Windows platforms only) If the Elasticsearch cluster, which is used by CloudBees Analytics, is in the red state (in Elasticsearch this means that it only partly functions and some data is unavailable) then upgrade reconfigure or uninstall operations will not work. Because the Elasticsearch service can not be stopped when a cluster is in red state kill the Elasticsearch service process by the task manager before running the installer for these actions.


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


Can’t ignore server mismatch and override passkey from Database Configuration page.


The ec-groovy command line utility fails when invoking createArtifactVersion with error This server cannot handle version <x> messages.


The warning, WARNING: An illegal reflective access operation has occurred is logged by Java 11 for the cglib library.


The LANG environment variable must be set to en.US.UTF-8; otherwise, the upgrade fails. For details, refer to KBEC-00452 - Error installing CloudBees CD 10.0.x when Lang environment variable is different than en.US.UTF-8.


In some cases, job step diagnostic information is not available and server reports 507 error, Missing sessionId attribute in request, when trying to view job step logs.


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


When you do a full import from version 8.0 to version 8.2 or newer and two or more releases have the same name (under different projects) and are associated to the same pipeline then after import the runs for all releases might become associated to the first imported release. This is because CloudBees CD/RO cannot differentiate runs between the releases since all runs are under the same pipeline project and have the same name. To work around this issue rename releases in the export file so that all their occurrences (in deploymentHistoryItem flowRuntime and so on) are unique.


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 setup for JIRA for user-stories and defects and the JIRA project name was mapped to the release project name using the following 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


Long custom labels in email notifications do not render correctly.


Approval by email on manual tasks should not expect parameters.


Navigation to a sub-release editor takes user to the parent release editor. As a workaround, select the subrelease from the left-hand navigation in the parent’s release editor.


When you use the Deploy UI to edit a resource pool and add a tag while renaming it at the same time, the operation fails with the following error: Resource pool 'oldPoolName' does not exist . To work around this issue, rename the resource pool, then save the change, and then add the tag to the resource pool.


Running an application process with a parallel manual application process step or running an application process with a parallel manual application and component process steps fails to delete the project.


If you are signed in to the Deploy UI and upgrade to CloudBees CD/RO 10.0, the version 10.0 sign-in page for the Automation Platform UI goes into an infinite redirect. This is because the version 10.0 Automation Platform UI thinks that your sign-in session expired even though it is active. To work around this issue, do one of the following:

  • Before upgrading, sign out from the Deploy UI and the Automation Platform UI.

  • After upgrading, sign out from the Deploy UI and then sign in.

  • After upgrading, clean your browser cache and cookies to kill the pre-upgrade sign-in session.


Attempt to delete a project containing a CIBuildDetails object (injected by Jenkins OSS or CloudBees CI) results in the error: The DELETE statement conflicted with the REFERENCE constraint.


Users will not be able to delete a project if there are Jenkins builds associated with this project that are references in releases not in the project.


Attempt to delete a build from a pipeline run via buildname and flowRuntimeId results in the error deleted object would be re-saved by cascade.


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 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 CD server UI. It is recommended to use ectool export and ectool import only between servers at the same version.


These service catalog items are disabled because underlying plugin has been removed.

  • Azure Container Service Discovery

  • Amazon ECS Dynamic Cluster

  • GCE Dynamic Cluster


Single Sign on 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 web server.


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.