Getting started

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.

CloudBees platform for SDM requires some initial setup before users can access it. As a CloudBees platform for SDM administrator, you will first need to:

  • Verify your account credentials provided by CloudBees.

  • Configure integrations for services like GitHub.

Accessing CloudBees platform for SDM

When you joined the Preview program, your existing or new CloudBees account has a new subscription for CloudBees platform for SDM. If an account was created for you as part of your Preview program on-boarding, you should receive initial administrative credentials for your CloudBees account and subscription management.

To access your CloudBees organization and user management:

  1. Go to app.cloudbees.com and sign in.

  2. From the upper right organization drop-down, select Manage organizations to update or modify an organization or Manage users to add or remove users associated with an organization.

  3. When redirected to CloudBees Network Portal, you may be prompted to log in again.

If you have any problems, contact support@cloudbees.com or your preview program coordinator at CloudBees.

You will need to add users for members of your team who will use CloudBees platform for SDM. Refer to Managing accounts for instructions on adding users and modifying an organization.

Forgotten password

If you forget your password, you can reset your password using this page: https://grandcentral.cloudbees.com/forgot-password

Setting up integrations

Integrating external services like GitHub lets CloudBees platform for SDM access data from these services. This data lets you monitor and manage the delivery of your products and features.

Integrating GitHub with CloudBees platform for SDM lets you add GitHub repositories to products so you can display branches, pull requests, commits, and branch status.

Integrating GitHub

CloudBees platform for SDM integrates with GitHub using the CloudBees Product Hub app, which connects a GitHub organization to your CloudBees platform for SDM account.

You need administrative rights on your GitHub organization to install the CloudBees Product Hub app. For additional information, refer to the GitHub documentation on permissions levels for organizations.

You can associate a GitHub organization with only a single CloudBees platform for SDM account currently.

To connect GitHub, you must install the CloudBees Product Hub app on GitHub. After you have connected GitHub to CloudBees platform for SDM, you can see your GitHub repository data in CloudBees platform for SDM. Then, you can link repositories and data to products to help you to prioritize work and locate blockers.

You must have administrative privileges in CloudBees to connect GitHub to CloudBees platform for SDM.

To connect GitHub to CloudBees platform for SDM:

  1. In the top right of any screen, select the organization name.

  2. Select Manage integrations.

  3. Select Add integration.

  4. On the Add integration screen, select GitHub, and then select Add.

  5. On the Add GitHub integration screen, verify that you want to install and configure the CloudBees Product Hub app, and then click Add.

  6. On the CloudBees Product Hub app screen, select Configure.

  7. Select the GitHub organization you want to associate with your CloudBees platform for SDM account. If you only have one account, that account is associated automatically. You may be prompted for your GitHub password.

  8. Select one of the following options:

    • To make all repositories in the organization available in CloudBees platform for SDM, select All repositories. All future updates will automatically be imported into CloudBees platform for SDM.

    • To allow CloudBees platform for SDM to access only specific repositories, select Only select repositories, and then select the repositories you want to add. Any time a new repository is added, you must update the list of approved repositories to import the updates into CloudBees platform for SDM.

  9. Select Install and Authorize.

Integrating Jenkins

Adding support for Jenkins integration is explained in the Jenkins integration section.

To remove an integration, refer to the GitHub integrations section.

Integrating Jenkins

Refer to Jenkins integration for instructions.

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.