Using integrations

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.

Viewing a list of active integrations

From the Integrations screen, you can see all of the external systems that are connected to CloudBees platform for SDM.

To view a list of active integrations:

  1. In the top right of any screen, select the organization name, and then select Manage integrations.

  2. (Optional) To narrow the list of integrations, in Filter integrations, type the name of the integration type that you want to see.

  3. Select an integration type to view more details.

Viewing connected GitHub repositories

All repositories that are available within CloudBees platform for SDM are listed on Integrations > GitHub. By default, they are sorted alphabetically by repository name. However, you can filter them by organization name instead.

Knowing the organization associated with the repository helps you to locate it.

When GitHub integration is configured, either all repositories from an organization are included or only selected repositories are included. If the repository you are looking for is not listed when linking a repository to a product, the CloudBees Product Hub app may be set to only import specific repositories.

To view connected GitHub repositories:

  1. In the top right of any screen, select the organization name, and then select Manage integrations.

  2. On the Integrations screen, select GitHub.

  3. On the Integrations/GitHub screen, select the organization that contains the repository you want to find. You should be able to locate the repository in the Repository name column. You can select the repository name to go to that repository in GitHub.

Viewing a list of connected Jenkins masters

The Jenkins integration uses the connected Jenkins masters data from DevOptics.

To view a list of connected Jenkins masters:

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

  2. Select Manage integrations.

  3. Select Jenkins Masters to open the DevOptics Connected masters screen.

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.