- Integration with CloudBees Feature Management
The Release Command Center dashboard (RCC) includes a new column that integrates with CloudBees Feature Management. The Feature Flags column shows metrics associated with feature flags configured for the current release. The CloudBees Software Delivery Automation EC-FeatureFlags plugin sources data from CloudBees Feature Management, which, in turn, supplies data to widgets in this new column. You configure the desired set of feature flags for your CloudBees Software Delivery Automation release from CloudBees Feature Management. You must have a CloudBees Feature Management license in order to source feature flag data.
Documentation: Release Command Center dashboard
Elasticsearch is upgraded from v7.10.2 to v7.13.4.
Logstash is upgraded from v7.12.1 to v7.13.4.
In the CloudBees CD/RO and CloudBees Analytics Continuous Integration Builds screen, if a build had a Running status, the Project column may not have displayed the project information, and the project information was only correctly displayed once the build completed. This issue has been resolved. If a build has a Running status, the Project column now correctly displays project information before the build has completed.
Build duration was published to CloudBees Analytics as a text field instead of a number. Starting with v10.3, the build duration report works with both text field and number.
The CloudBees Analytics dashboard parameter could not be passed as a parameter to the widget using the
JIRA storyPoints value was not published to CloudBees Analytics Release Command Center since it is not a number.
This section provides information about upgrading the CloudBees Analytics server.
Upgrading CloudBees Analytics clusters
The principle of forming a cluster in CloudBees Analytics has changed in v10.2 due to the update of Elasticsearch v7.10.2. In this regard, an additional action is required to upgrade to CloudBees Analytics v10.2 or later:
When updating the first master node, the user must explicitly specify that it is the first node to be updated. If this action is not performed, a cluster being updated is placed out of service.
All installers have been instrumented to accommodate this change. See Upgrading the CloudBees Analytics server for more details. [BEE-2717]
CloudBees Analytics server configuration notes
For a production environment, CloudBees recommends that you install the CloudBees Analytics server on a system other than systems running other CloudBees Software Delivery Automation components (such as the CloudBees Software Delivery Automation server, web server, repository server, or agent). If you must install it on the same system (such as for testing or other non-production or trial-basis situations) see CloudBees Analytics server with other components for details.
(Windows platforms only) If the Elasticsearch cluster, which is used by CloudBees Analytics, 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. Since the Elasticsearch service cannot be stopped when a cluster is in red state, kill the Elasticsearch service process using the task manager before running the installer for these actions.
Jobs might not appear upon drill-down into the "Clusters With Most Deployments" widget in the CloudBees Analytics Microservices Dashboard if the service does not contain a deploy step in the process.
The ability to search by assignee in a Deployment Report is not available in the CloudBees Analytics report editor.