CloudBees CD 2020.10.00 preview release notes

9 minute read

CloudBees is pleased to announce the availability of the CloudBees CD 2020.10.00 preview release.

Release notes for previous preview releases:

New features and functionality

Security updates


Audit and compliance reports

Native audit reports are now available in CloudBees CD. These reports aggregate data generated and collected throughout CloudBees CI and CloudBees CD processes into easy to read reports that address auditing requirements of CloudBees CD customers.


External credential management support

Credential management capability has been extended to support external credential providers. External credentials are abstracted from the external management system and stored in CloudBees CD as references. Workflow to attach external credentials to plugins, procedures, and steps is identical to that for local credentials. At runtime, external credentials are retrieved on-demand from the external management system. [NMB-29479]

Supported external credential management systems include:

  • CyberArk: Dynamic Access Provider (DAP) and Central Credential Provider (CCP)

  • HashiCorp Vault: CUBBYHOLE, KV1 and KV2 secret engines

CloudBees CD UI support added to define external credential manager provider

CloudBees CD API changes:

  • Added new CredentialProvider API.

  • Enhanced Credential Management API with new credentialProviderName to reference provider for external credentials.


Enhanced discovery for CloudBees CI controllers

Completed integration where CloudBees CD can now connect directly to a CloudBees CI operations center to automatically discover and update the list of connected controllers on which a CI Job CloudBees CD pipeline task can run, amplifying the value across both products. This streamlines creation and management of controller configurations. [CEV-25661]

  • Enhanced CI configuration UI to support CloudBees CI operations center configurations.

  • Added support to discover CI Controllers from CloudBees CI operations center.

API changes:

  • Added support to filter CI configurations by ciConfigurationType.

  • Enhanced the CI_JOB task type to support referencing a CI Job using a CI Configuration of type CB_OPS_CENTER CI configuration.


Updated Schedules UI page

The Schedules automation platform page is now available from the CloudBees CD UI via DevOps Essentials Schedules on the main CloudBees CD menu. [NMB-25556]

Proxy support for CloudBees CD agents

Server-side environment variable definition support added for job steps running on the agent. These properties may be created under zone and/or resource entities in the special ec_environment_variables property sheet. If ec_environment_variables property sheet does not exist, manually create it under zone and/or resource objects to define environment variables. [NMB-29614]

  • Property to define environment variable for http proxy resource

      -> properties
        -> property sheet ec_environment_variables
          -> http_proxy = http://user:password@your-proxy-ip-address:port/
  • Property to define environment variable for https proxy resource

      -> properties
        -> property sheet ec_environment_variables
          -> http_proxy = https://user:password@your-proxy-ip-address:port/

Expanded --filters parameter support with ectool

The getPipelineRuntimes API now supports the --filters parameter when invoked with ectool. [CEV-25946]

CloudBees CD plugin updates


  • Fixed parameter handling when the plugin is used in a component process step. [FLOWPLUGIN-8626]


  • Changed configuration handling: If a file is provided for the configuration, the file is used, if the content of configuration file is provided, a temporary file is created to use with the plugin procedures. [FLOWPLUGIN-8643]

  • Fixed an issue with spaces in Helm chart path. [FLOWPLUGIN-8595]


  • Added token cleanup (logout) at each plugin step. [FLOWPLUGIN-8614]


  • The Artifact2Image procedure now supports Artifactory extract boolean and classifier.[FLOWPLUGIN-7818, FLOWPLUGIN-7817]

Plugin support changes

The following plugins are being moved to community support going forward as of CloudBees CD preview release 2020.10.0. Log change requests or issues on their respective GitHub projects. Customers are encouraged to explore changing these plugins directly as required.


































Plugin developer guide availability

The Plugin Developer Guide is now available on the main product doc site. [CEV-25554]

Behavior changes


Resolved issues


Improved StepScheduler run performance to prevent deadlocks when processing and scheduling steps.


The runProcedure --pollInterval command now polls beyond 60 seconds when --timeout is greater than 60 seconds.

Installation notes

CloudBees CD preview releases support clean installations, only. For complete installation information, see Installing CloudBees CD on Traditional Platforms or Installing CloudBees CD on Kubernetes.

New CloudBees CD release strategy

Starting in January 2020, the release strategy for CloudBees CD is updated to add a preview release in addition to the standard long-term support (LTS), maintenance (patch), and hotfix releases.

The release numbering for the preview releases uses a new year.month.00 numbering scheme. For example, 2020.01.00.

This release is meant to be used in test environments to try out the new features and provide feedback. Upgrades from previous LTS releases as well as from previous preview releases are not supported.

For details about the new release strategy, see CloudBees CD release strategy.


  • When an application is cloned from one project (the original project) to another (the destination project), the tier maps for the application will 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


Some antivirus software might flag parl.exe and delete it, which causes the installation to fail. The workaround is to register this file in the acceptlist of the antivirus.


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 do not appear properly in user details (in the Automation Platform UI, the Deploy UI, or ectool ) until the CloudBees CD server is restarted.


(Windows platforms only) If the Elasticsearch cluster which is used by DevOps Insight 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. See KBEC-00452 - Error installing CloudBees CD 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 6.1 or earlier is cloned and a project containing this application is imported to CloudBees CD 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 DevOps Insight 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 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 DevOps Insight 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":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 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 LTS 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


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 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 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 see change tracking.


CloudBees CD documentation for the this preview release is available at the CloudBees CD documentation site.

Documentation on the website is updated periodically.

Troubleshooting and getting help

Contacting CloudBees Support

To contact CloudBees Support, go to and then click Submit a request to submit or see your support tickets.

Be prepared to provide your:

  • Name, title, company name, phone number, and email address

  • Operating system and version number

  • Product name and release version

  • Problem description

CloudBees CD "Ask" Website

Go to — a member-moderated community forum where you can:

  • Ask and answer questions as well as comment on (and vote for) the questions of others and their answers

  • Get help with installation and configuration

  • Submit feedback

CloudBees CD Knowledge Base

Go to to find in-depth explanations of specific topics and solutions.