CloudBees CD 2020.05.00 preview release notes

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

Release notes for previous preview releases:

New features and functionality

Security updates

  • PHP is upgraded from version 7.2.30 to 7.4.6. For details, see

Improved CloudBees CD and CloudBees CI integrated experience

CloudBees CD agent on MacOS Catalina

CloudBees CD agent is now supported on MacOS Catalina. [NMB-28785]

CloudBees CD on Kubernetes

  • Helm chart deployment on Red Hat OpenShift has been certified. [NMB-28920]

Application Deployments list

  • The Application Deployments list can now be sorted by clicking the column headers. [CEV-24078]

CloudBees CD plugin updates


  • Added error-resistant handling of PEM RSA private key: base64 body validation, beginning and end markers, number of pads. [FLOWPLUGIN-8290]


  • Deprecated usage of depth parameter in API calls has been removed. [FLOWPLUGIN-8303]

Jenkins plugin updates

  • Improved integration with CloudBees CD:

    • CI Build Data infrastructure has been created.

    • Event-based watchers have been created to send build data to CloudBees CD automatically if build has been triggered by CloudBees CD.

  • Support for new CloudBees CI build detail APIs:

    • New post-build action: Associate build to release to allow attaching CloudBees CI build data of the independent builds to releases or release runs.

    • TriggerPipeline now attaches CloudBees CI Build Data to the triggered pipeline run.

    • TriggerRelease now attaches CloudBees CI Build Data to the triggered release pipeline run.

Behavior changes


Resolved issues


Slow response on the Pipeline Run list page due to getPipelineRuntimes,getPipelineRuntimeDetails, and getPipelineStageRuntimeTasks commands clogging API threads.


Issue resolved with pipeline workspaces disappearing in some circumstances.

Installation Notes

CloudBees CD preview releases support clean installations, only. For complete installation information, see Installing CloudBees Flow on Traditional Platforms or Installing CloudBees Flow 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 Flow 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


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


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.


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


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.


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.



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.


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


Performance for the pipeline runtime list page is slow.


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.


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.


Long custom labels in email notifications do not render correctly.


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 9.2 the field mapping must be updated to mention the actual release project name using the following field mapping format: release-project-name-in-CloudBees Flow:releaseProjectName

CEV-19259, CEV-19239

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


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


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.


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.


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


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


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


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.


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


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


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


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.


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 Flow documentation page.

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.