CloudBees Flow preview release notes

7 minute read

CloudBees is pleased to announce the availability of the CloudBees Flow 2020-01-00 preview release.

New CloudBees Flow release strategy

Starting in January 2020, the release strategy for CloudBees Flow 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 maintenance lifecycle policies.

2020.01.00 new features and functionality

This release delivers innovation across many vectors such as:

Security updates

This release includes the following security updates. [NMB-28922]

Flow on Kubernetes

  • Helm 3 support. [NMB-28916]

CloudBees Flow plugin updates


Provides ability to optionally pass ServiceNow display values in addition to ServiceNow system identifiers.

CloudBees Flow Plugin

This plugin is now fully Jenkins pipeline compatible with the addition of ability to publish artifacts and create and deploy applications from deployment package post-build actions. It is available in both Jenkins LTS and CloudBees Core.


This plugin is enhanced to surface more detailed build information for Jenkins Pipelines and creates new HTML Reports.


Introduced in this preview release, EC-Helm supports both Helm 2.0 and Helm 3.0 and OpenShift as well as Kubernetes deployments. Documentation for this plugin provides instructions for how this plugin can be used, for example, to spin up CloudBees Core in GCP.


Fixes to access the plugin catalog through HTTPS.

Flow Plugin Development Framework


Enhanced to provide support for developing flow plugins using Groovy. The new libraries for Groovy as well as detailed tutorials for many sample Groovy-based plugins are documented in the Flow Plugin Developer Guide.

Flow plugin dependency management improvements

  • Provisioning of binary dependencies (for example Grape jars) in the agent resource, required by a plugin, is now seamlessly delivered through a new feature called Plugin Dependency Management in the CloudBees Flow server.

  • A new DSL based fallback provisioning mechanism is introduced for older versions of CloudBees Flow server. Plugins that uptake this feature no longer require CloudBees Flow repository to be setup in order to function. The following plugins have completely uptaken this feature: EC-Kubectl, EC-EC2, EC-Ansible, EC-AmazonECS, EC-RemoteAccess. Look for more plugins incorporating this in the next release. [NMB-27689]

DSL editor improvements

  • Allow inline edit and save for DSL without opening modal. [CEV-24099]

  • Sort and maintain nested objects in alphabetical order when saved. [CEV-24094]

Release hierarchy improvements

Improvements to hierarchy data fix: a new background trigger is introduced which allows users to fix the hierarchy data for flowRuntimes which were created before CloudBees Flow v9.2. [CEV-23898]

This trigger does the following:

  • Fixes hierarchy data as a background operation in batches.

    • Wakes up every 2 minutes and fixes the flowRuntimes that require a data fix and fixes it, in batches of 100 each time.

    • Once a flowRuntime record is fixed, changes the flag requiresHierarchyDataFix to 0.

  • Allows user to switch off/on this background operation.

  • Provides a server setting that allows users to turn off the hierarchy data fix operation:


    Users can set this flag to false if they wish to stop the hierarchy data fix in the background.

Release pipeline enhancements

Triggered pipelines can now be attached to a release. [CEV-23963]

Revised automated platform Resource UI

The Resource page, previously available only via the Automated Platform UI, is now available from the Deploy UI. [CEV-23151]

2020.01.00 Behavior Changes


New precautions are in place to prevent the Everyone group from being deleted. For more details about the Everyone group and access control, see Configuring access control

2020.01.00 Resolved Issues


Fixed issue when updating an existing pipeline via the DSL editor caused a spurious InvalidResourceName exception if resourceName='' (resourceName as an empty string) was specified.


Fixed an issue where, in some circumstances, the job details page of a deployer task inside a release pipeline appeared blank.


A catalog item based on a procedure with a credential as a required parameter can now be launched.


Fixed an issue where setting the approver via property and selecting the JavaScript Format checkbox from the UI for a manual task inserts invalid javascript syntax resulting in an invalid approver name. As a result, the task could not be approved.


Fixed an issue when a pipeline, copied from project A to project B with waitForTriggeredPipelines configured, had dependentProjectName set to project A instead of project B.


Resolved a problem where the sign-in page went into infinite redirect after upgrade from 9.1 to 9.2.


Resolved an issue where LDAP users were placed into a persona but not showing up in the persona editor.

Installation Notes

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


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


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 Flow 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 Flow 6.1 or earlier is cloned and a project containing this application is imported to CloudBees Flow 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 Flow 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 Flow 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.


Flow documentation for the latest technical preview release is available at CloudBees Flow

Documentation on the website is updated periodically.

Troubleshooting and Getting Help

Technical Support

To contact CloudBees technical 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 Flow Knowledge Base

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