Getting started with CloudBees platform for SDM

CloudBees platform for SDM is a preview, with early access for select preview members. Product features and documentation are frequently updated. If you find an issue or have a suggestion, please contact support@cloudbees.com.

Linking your data and resources from software delivery systems can help you understand the work involved and the current status of that work. Using CloudBees platform for SDM, you can model the products your organization delivers.

This guide explains how to set up your first product and track its repository health and delivery blockers. When you are finished with this section, you can:

  • Model the products in your organization.

  • Link Github data to your products.

  • Track product health and identify repositories that need your attention.

  • View pull requests that are blocking software delivery.

The CloudBees platform for SDM content page provides details about supported platforms and services as well as the preview.

Accessing CloudBees platform for SDM

To access the CloudBees platform for SDM, log in to app.cloudbees.com.

The active organization is displayed next to your profile picture in the upper right corner.

To view your CloudBees organizations:

  1. Select the current organization to display a list of the organizations you belong to.

  2. Choose another organization from the list, if desired.

About products

A product is any organized work effort that addresses a market need, either internal or external, and delivers an intentional user outcome. The product provides a way to organize the work involved and the current status of that work.

The number of products you create in CloudBees platform for SDM should mirror the organization of work that needs to be tracked. Let’s say that your team works on three offerings: Solution One, Solution Two, and Solution Three. You would create a product for each solution and then associate repositories for those defined products.

For more information about products, refer to Using products and product hub.

Creating a product

To create a product:

  1. Select Product hub.

  2. Select Create product, or Create new product if this is the first product.

  3. Enter a name for the product, and then select Create.

The new product name appears on the Product hub.

Once the product is created, you can use the options menu (three vertical dots) to edit the product name or delete the product.

Linking GitHub repositories with a product

To add GitHub repositories to a product:

  1. Select the product name from the Product hub.

  2. On the left pane, select Repositories.

  3. Select Link repository or, if this is the first time you are adding repositories, select Link your first repository, to display a list of available repositories.

  4. Choose the repositories to associate with the product. You can filter the repositories list by entering a complete or partial repository name in the text box or by selecting a GitHub organization from the Organization drop-down.

  5. Select Save changes.

Linking pipelines and jobs with a product

Linking Jenkins jobs and pipelines allows you to add build and job information to products. Selecting a Jenkins job links the job and any pipelines with the chosen product. Jenkins masters need to be connected before you can link jobs and pipelines to products.

Each job can be linked to one or more products.

To link pipelines:

  1. From the Product hub, select a product.

  2. Select Jobs.

    • If this is the first time you are linking a pipeline, select Link your first job.

    • Otherwise, select Link jobs.

  3. Select one or more check boxes to associate those jobs with the product. Select Save changes.

Tracking product health

Now that you have created your first product and linked repositories, you can track product health by monitoring pull requests for each product.

Any issues with pull requests are summarized on the product Overview. These issues are highlighted with status labels.

To track product health by reviewing pull requests:

  1. From the Product hub, select a product.

  2. Select a repository link to view a detailed list of pull requests for that repository.

  3. Look for any status labels indicating issues with pull requests.

Identifying pull request delivery blockers

The pull requests for a product’s repositories are listed on the product’s Pull requests screen. Status labels, listed in the Status column, indicate if there are any pull request issues and their severity.

Using these status labels as a guide, you can identify potential blockers and address them.

To identify pull request delivery blockers:

  1. From the Product hub, select a product.

  2. In the left pane, select Pull requests.

  3. At the top of the Status column, select the red, green, or yellow icon to filter the list.

The Created by column lists the name of the person who originally opened the pull request. They may be able to help resolve issues.

To view the GitHub page of the pull request creator:

  1. From the product’s Pull requests screen, locate the name of the person in the Created by column.

  2. Select the person’s name to view their GitHub profile.

Next steps

After you have created your first product and associated data with it, you can monitor repository health and identify potential blockers by:

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.