Configuration

Configure DevOps Foresight in CloudBees Flow

  1. Sign in to CloudBees Flow and go to Self-Service Catalogs by selecting the self service catalogs icon on the top of the screen.

  2. Navigate to the Configure DevOps Foresight item and click Configure .

  3. Enter the DevOps Foresight Server URL . This is the URL for accessing the DevOps Foresight server; for example, http://<foresight_server_hostname>:8080. configure dofs

  4. Enter the Frequency at which to run analytics for CI risk predictions (in minutes) .

  5. Click OK to configure DevOps Foresight.

DevOps Foresight basic configuration is complete.

Configure Data Collection

CloudBees Flow includes several plugins in the that you can configure to periodically collect Continuous Integration (CI) data from third-party tools and send it to the DevOps Insight server. DevOps Foresight uses this data for predictive analytics. The following table shows the CI-related data sets and corresponding plugins that can be used to collect data.

Data set Third-party Tool CloudBees Flow Plugin

Build, and Change sets

Jenkins

EC-Jenkins

Code Commits

Git

ECSCM-Git

Code Quality (static code analysis)

SonarQube

EC-SonarQube

As part of DevOps Foresight, a utility procedure is added in the CloudBees project, out of the box, to aide in plugin setup. These procedures are available from CloudBees Flow via the Platform/projects page in the Automation Platform web UI: browse to https:// <CloudBees Flow_server> /commander/, and then click Administration > Platform/projects . For more information about them see the CloudBees Flow User Guide.

Utility Procedure in CloudBees Project Plugin Description

Jenkins Setup for Command Center - build and quality

EC-Jenkins

This is an existing procedure that is also used to setup EC-Jenkins for the Release Command Center. If the procedure was already used to set up Release Command Center, then the schedule that was created for the same may be updated as required for DevOps Foresight.

Git Setup for DevOps Insight

ECSCM-Git

This is a new procedure added as part of DevOps Foresight.

SonarQube Setup for DevOps Foresight

EC-SonarQube

This is a new procedure added as part of DevOps Foresight.

Once the CI risk predictions analytics start running on the scheduled frequency, you can start seeing Risk Predictions , and more, through DevOps Foresight.

dofsrisk predections dashboard

Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at www.cloudbees.com/jenkins/about. Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.