CloudBees CD/RO v2023.10.0

Java has been updated to the latest version - 17.0.7.

Updated Jetty from v11.0.15 to v11.0.16.

Updated BouncyCastle to version 1.76 to improve security.

Enhanced security by using MessageDigest.isEqual(..) for license digest comparison.

Changed SSLContext.getInstance("TLS") to SSLContext.getInstance("TLSv1.2") in the code.

Based on insights from the EC-DslDeploy plugin, the new dslsync CLI-based utility extends the functionality of the generateDsl and evalDsl APIs to help manage and promote DSL across multiple files and directories in a GitOps and IDE friendly manner. However, dslsync also adds intelligent DSL evaluation based on Git logs, including actions for delete, modify and apply only changes. Additionally, and unlike EC-DslDeploy, you can run dslsync commands directly from your CLI without requiring a CloudBees CD/RO agent.

Support for systemd service management system has been added to Linux platform installers. To ensure backward compatibility, systemd is only used in environments where the System V service management system is not supported. Additionally, you can now explicitly specify a service management system using the command line parameter --useServiceManagement when running Linux platform installers.

You can now create catalog items based on existing releases. Once created, the item appears as an option in the Releases  New  Create from catalog item…​ dialog. For more information, refer to Save release as catalog item.

Task hook functionality is now available in CloudBees CD/RO v2023.10. This feature allows the addition of a procedure or command as the last step of task. Adding a task hook extends functionality of plugins and third-party deployers by enabling log parsing, extraction of deployment data and updating of the environment inventory.

ARM Linux is now supported as a first class platform in CloudBees CD/RO along with the existing support for x86 64-bit Linux, Windows and Mac. This includes Mac M1 through Rosetta II emulation.

A new admin-readonly system user has been added. This user is enabled once the admin sets a password for it and will have all the same read privileges as the admin user.

CloudBees CD/RO Helm charts now supports Kubernetes v1.26.

CloudBees CD/RO Helm charts now support Kubernetes v1.27.

The following components have been updated:

Tasks are enhanced with unifying behavior; selecting a task name opens the task definition. A link will be present when the task references a procedure, pipeline, or release, allowing the user to navigate to the object’s definition.

You can now search for a plugin and select one without having to select a category.

To improve usability, you no longer have to install and configure the EC-ServiceNow plugin to use the mean time to recover (MTTR) and change failure rate (CFR) dashboards.

CloudBees CD/RO on Kubernetes Helm chart now supports global values for configuring image settings used by the chart in a single place in the cloudbees-flow values file. When set, global values override the corresponding values set at the component level. For more information, refer to How to set global values in CloudBees CD/RO Helm charts.

Added support for suppressEmpty into the Export DSL catalog item.

Support to use custom CloudBees Analytics init container images was added to the 2023.10.0 Helm charts and values file. For more information, refer to How to install custom CloudBees Analytics init container images.

You can now specify an internal image that contains wget. This image is not required for installing and running CloudBees CD/RO on Kubernetes. It is only used by tests included in the cloudbees-flow and cloudbees-flow-agent charts. Previously, the tests relied on a public repository, which may not have been accessible in certain environments.

Elasticsearch has been updated to v7.17.12.

Where applicable, you can now select multiple options in dropdown menus for formal parameter types:

Now allowing substitution special characters $[] to be used.

In CloudBees CD/RO v2023.10, the ability to convert a service catalog item into a release template was added. Once converted, this template can be used to create new releases from the catalog item. Refer to: Convert service catalog item into a release template

CloudBees CD/RO now supports using custom certificates issued by custom chained certification authorities, as well as managing CRLs as files or distribution points.

Within EC-DslDeploy procedures, you can now import serviceAccount objects.

Added new numberToRetain argument for the createDataRetentionPolicy and modifyDataRetentionPolicy APIs to allow the retention of a given number of the most recent items as specified by the numberToRetain argument.

The CloudBees CD/RO plugins catalog is available on the CloudBees CD/RO documentation site.

Fixed DSL property name issue that created conflicts between parent context objects and their nested operation arguments.

Calls to the getPipelineRuntimes API in REST and in ec-groovy can now be made without arguments.

Fixed the misinterpretation of transaction rollback errors returned by the RDBMS when committing transactions.

In situations where sub-pipelines with manual approver tasks were triggered by a main pipeline, the user context of the manual approver was incorrectly applied to the LaunchedByUser context of the main pipeline. This issue has been fixed, and now the LaunchedByUser contexts of main pipelines are unaffected by manual approver contexts of sub-pipelines.

Resolved an issue where a task could not be disabled after being added to a group.

With this release, breaking inheritance at one level does not break inheritance beyond that level.

Solved the problem of catalog item process failing, because of missing default value by adding default value of False to the replaceObjects parameter of validateFormalParameter API.

Resolved an issue where the DSL editor did not work correctly when the object name included a slash.

When changing a step type from subprocedure to command, non-applicable actual parameters are now automatically removed.

The MeanLeadTime report does not work correctly when Elasticsearch only has pipeline runs but no release runs.

The CloudBees CD/RO UI does not allow you to transfer artifacts across zones.

When a custom data retention policy schedule is set to run once, the data is not purged after archiving. To purge data after archiving, use a repeat schedule or the global data retention setting.

When using PostgreSQL with change tracking enabled, EcAuditStrategy errors may appear in the server log. This is a known issue, but is not expected to have any effect on the performance of the system.

Events that originate from the default CloudBees CI create default configurations. URLs for these new controllers are not Jenkins configured URLs and cause 401 errors.

You may experience SSO sign-in issues when using Kerberos due to a Microsoft known issue.

When a process step that is not manual is modified to be manual after the process runs, but before the associated job step evaluated, the step hangs and adds a java.lang.IllegalStateException: Unknown step type: manual exception to the log.

The flowRuntime response contains hasCIJobs=1 if a release was started from CloudBees CD/RO and the previous release run was triggered within CloudBees CI.

On Windows agents, "Export DSL" catalog item fails to export objects that end in spaces.

When running getCIBuildLog for a CloudBees CI build, the build log cannot be accessed without restarting the build CloudBees CI controller. As a workaround, restart your CloudBees CI controller, and set up a number of executors, and getCIBuildLog can then be used to access the CloudBees CI build logs.

Before upgrading from CloudBees CD/RO v10.2 and earlier, if legacy services exist in your system, upgrades may fail and database consistency break. Additionally, even if the upgrade returns successfully, it may still be impossible to run the validateDatabase API.

In CloudBees CI job responses, actual parameters are returned that are not defined within the job. Additionally, saving and reloading the tasks doesn’t clear undefined actual parameters.

Currently, if a formal parameter depends on a dropdown menu to get project parameter dependencies for object-like parameters, such as projectName, you can select multiple options in dropdown menus. However, there is only an object name (or list of names in case of multi-select) in the parameter value with no connection to a project and without the ability to identify which object exists in which projects.

When updating from v10.2 or earlier to v10.3 or later, your upgrade may fail and break database consistency if legacy services or containers exist in your system. Additionally, even if the upgrade completes successfully with legacy services or containers present, it may still be impossible to run the validateDatabase API.

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.

(Microsoft Windows platforms only) If the Elasticsearch cluster used by CloudBees Analytics is in the red state (meaning that it only partly functions and some data is unavailable), then upgrade, reconfigure, and uninstall operations will not work. Since the Elasticsearch service cannot be stopped when a cluster is in a red state, you must stop the Elasticsearch service process from the task manager before running the installer for these actions.

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

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

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

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

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.

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

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

If Release Command Center was set up for Jira for user stories and defects, and the JIRA project name was mapped to the release project name using the 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.

Approval by email on manual tasks should not expect parameters.

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

SSO does not work unless PHP configuration is changed due to a security-related request. As a workaround, change session.cookie_samesite to "Strict" in /opt/electriccloud/electriccommander/apache/conf/php.ini and restart the web server.

CloudBees CD/RO v10.1 introduced new triggers and an updated UI for them. Pre-v10.1 triggers will continue to work but there is no UI to review or run them.

Before using the export command to perform a full data export from the CloudBees CD/RO database, delete any legacy definitions and references to service objects from applications and releases.

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

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

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]:

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