Existing installations of CloudBees CD on Kubernetes can take advantage of the analytics capabilities of CloudBees Software Delivery Automation.
CloudBees provides a Helm chart to install the components required to enable end-to-end data flow from CloudBees CI to the analytics dashboards in CloudBees Software Delivery Automation.
The Helm chart:
-
Includes the CloudBees CI on modern cloud platforms and CloudBees CD Helm charts.
-
Preconfigures the URL for the server to which analytics events are sent.
-
Installs the components needed for analytics: the CloudBees Software Delivery Automation analytics server, the webserver, MariaDB, and the CloudBees Analytics server.
-
Automatically creates the Ingresses required to access CloudBees CD, CloudBees CI, and CloudBees Software Delivery Automation analytics.
Pre-installation notes
Before upgrading CloudBees CD, you should become familiar with CloudBees CI and CloudBees Analytics concepts and terminology, which is referenced throughout the installation documentation. See CloudBees Analytics architecture for more information.
In addition, review the following important information:
-
The
sda-chart
Helm chart installs CloudBees CD, the CloudBees CI operations center, all required CloudBees CI plugins, and the CloudBees Software Delivery Automation analytics components on the same Kubernetes cluster and in the same namespace. -
CloudBees CD plugins are not installed.
-
After installation, the credential needed to enable communication from CloudBees CI to CloudBees Software Delivery Automation analytics is configured automatically.
-
The
sda-chart
Helm chart is located in the same repository as the CloudBees CD Helm chart: https://public-charts.artifacts.cloudbees.com/repository/public/
Upgrading CloudBees CD to add CloudBees Analytics
To update CloudBees CD on Kubernetes to CloudBees Software Delivery Automation:
-
Add CloudBees Software Delivery Automation to your CloudBees CD installation:
-
In your existing versioned
value-overrides.yaml
file, do the following:-
Move the existing values under a
cd:
subsection. -
Create a
ci:
subsection, and then duplicate thecd.ingress.host
toci.OperationsCenter.HostName
and duplicate thecd.ingress.certificate.existingSecret
toci.OperationsCenter.Ingress.tls.SecretName
.
-
-
Perform the upgrade:
helm upgrade -f /path/to/edited/value-overrides.yaml your-release-name cloudbees/cloudbees-sda
Verifying the installation
-
Type the following command:
kubectl get po
-
Verify that items with the following prefixes appear:
-
cjoc
-
flow-bound-agent
-
flow-devopsinsight
-
flow-server
-
flow-web
-
mariadb
-
managed controller names
-
Setting up the connection to CloudBees Software Delivery Automation
-
From your CloudBees CI operations center, go to Manage Jenkins, and then scroll down to Connection to CloudBees Software Delivery Automation.
-
In URL of the CloudBees Software Delivery Automation server, verify that the URL for the CloudBees Software Delivery Automation server has been configured. For example,
https://your.hostname/
. This should just be the same as the CloudBees CI operations center URL minus thecjoc/
suffix. -
Check that Connected successfully is displayed, and then click Save.
Do not change the Allow analytics events to be sent and Send analytics events to this URL fields. These fields are populated automatically to enable analytics events to flow from CloudBees CI to CloudBees Software Delivery Automation. |
Signing in to CloudBees Software Delivery Automation
-
Follow the instructions in the Helm chart to obtain the password.
-
Go to
https://your.host/flow/
and sign in using the user nameadmin
and the password obtained from step 1.
Configuring CloudBees CI controllers
Now, follow instructions here to configure operations center and CloudBees CI controllers.
Administration tasks
After you have installed CloudBees CI on traditional platforms and upgraded CloudBees CD, the following items are created in CloudBees CD during the first server startup:
-
The CloudBees Software Delivery Automation license to grant access to CloudBees CD data and the API that are required to pull and view CloudBees Analytics data.
-
The CloudBees Software Delivery Automation persona menu items configured for the CloudBees Analytics context.
-
An
admin
user with a default password,changeme
, that has the CloudBees Software Delivery Automation persona and license associated with it.
Create user accounts: from the main menu, select
or .Add users to the CloudBees Software Delivery Automation persona: see Personas for details.