CloudBees Flow preview release notes

CEV-23976

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

CEV-23972

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.

CEV-23713

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

CEV-22960

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

CEV-23989

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.

CEV-24049

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.

CEV-23960

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

CEV-23199

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

NMB-28381

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

NMB-28135

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.

NMB-26962

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

NMB-26021

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.

NMB-24949

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 .

CEV-23959

Performance for the pipeline runtime list page is slow.

CEV-23958

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.

CEV-22644

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.

CEV-22379

Long custom labels in email notifications do not render correctly.

CEV-21426

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.

CEV-18531

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

CEV-17164

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.

CEV-16930

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.

CEV-16250

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

CEV-16245

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

CEV-15829

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

CEV-15122

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.

CEV-14689

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

CEV-12429

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

CEV-12363

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

CEV-11106

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.

N/A

You can revert changes only for high-level design objects such as applications procedures procedure steps workflow definitions and state definitions.

N/A

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.

N/A

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.